# How to access aggregations from within custom request handler

**URL:** <https://discuss.elastic.co/t/how-to-access-aggregations-from-within-custom-request-handler/226445>\
**Category:** Kibana\
**Created:** [April 3, 2020, 5:24pm UTC](https://discuss.elastic.co/t/how-to-access-aggregations-from-within-custom-request-handler/226445 "2020-04-03T17:24:41Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![lukeelmers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukeelmers/32/35230_2.png) [@lukeelmers](https://discuss.elastic.co/u/lukeelmers)\
**Post date:** [June 1, 2020, 11:32pm UTC](https://discuss.elastic.co/t/how-to-access-aggregations-from-within-custom-request-handler/226445/5 "2020-06-01T23:32:27Z")

</div>

Just wanted to leave a note that it looks like this was removed for custom request handlers as part of migration efforts in our visualization infrastructure, but I don't believe we did this intentionally (in short: it's a bug). There has been a lot of churn in our visualizations which I explain in more detail in [Request/Response handlers in visualizations](https://discuss.elastic.co/t/request-response-handlers-in-visualizations/221727/2) and the corresponding Github issue.

At the moment I believe this would affect any plugins in 7.5-7.7 registering visualizations which are also using a custom requestHandler that needs access to aggs.

I'm working to get this re-added soon... Here's the Github issue if you'd like to follow along: [https://github.com/elastic/kibana/issues/67916](https://github.com/elastic/kibana/issues/67916)

---

_[View the full topic](https://discuss.elastic.co/t/how-to-access-aggregations-from-within-custom-request-handler/226445)._
