# Get original Elasticsearch response instead of tabify **URL:** \ **Category:** Kibana\ **Created:** [April 26, 2020, 6:37am UTC](https://discuss.elastic.co/t/get-original-elasticsearch-response-instead-of-tabify/229815 "2020-04-26T06:37:13Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![ssimmons](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@ssimmons](https://discuss.elastic.co/u/ssimmons)\ **Post date:** [April 26, 2020, 6:37am UTC](https://discuss.elastic.co/t/get-original-elasticsearch-response-instead-of-tabify/229815/1 "2020-04-26T06:37:14Z")
Is there a way to get the original Elasticsearch response in Kiabana instead of the tabified response? I found a thread where it was stated you could set your response handler to 'none' and that would return the original Elasticsearch response, but this was for version 6.1 of Kibana and I'm using version 7.5. I've tried setting my response handler to `responseHandler: 'none'`, but I'm still getting back a tabify response. Is it possible to get an non-tabify response with version 7.5? ---
**Author:** ![ppisljar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppisljar/32/11588_2.png) [@ppisljar](https://discuss.elastic.co/u/ppisljar)\ **Post date:** [April 28, 2020, 12:13pm UTC](https://discuss.elastic.co/t/get-original-elasticsearch-response-instead-of-tabify/229815/2 "2020-04-28T12:13:32Z")
in what context are you trying to achieve this ? i am guessing you are trying to add a new visualization type ? no, that is not possible, we changed the architecture of visualizations trying to decouple them from data fetching. For this reasons visualizations are not given any raw es responses but rather a datatable which we use as a common data model. There is also no information about the aggregations you ran and so on, as the idea is the visualization should not care where the data came from, which allows us to reuse same visualizations for different data fetching methods. what you most likely want to do is implement your own embeddable. Where visualization is responsible only for rendering and should not care where the data comes from, embeddable does the data fetching and gives the data to visualization (or you don't need visualization at all, embeddable does rendering as well. However that will not allow you to reuse the default editor, you will most likely end up writing your own kibana app which will serve as the editor for your embeddable. ---
**Author:** ![ssimmons](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@ssimmons](https://discuss.elastic.co/u/ssimmons)\ **Post date:** [April 28, 2020, 1:26pm UTC](https://discuss.elastic.co/t/get-original-elasticsearch-response-instead-of-tabify/229815/3 "2020-04-28T13:26:40Z")
Thank you for the detailed response. You are correct in that I'm writing my own visualization. I use bucket aggregations and I'm trying to find ways around the issue of the aggregations not being accurate at times. What I found was the count that is returned for the ` __other__ ` bucket with the tabify response can be a lot different than the count for the `sum_other_doc_count` parameter that gets returned with the raw ES response. I've found the `sum_other_doc_count` to be more accurate and I wanted to use that count instead of the ` __other__ ` bucket count for calculating the percentages. I'll look into the embeddable. Thanks. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 26, 2020, 1:26pm UTC](https://discuss.elastic.co/t/get-original-elasticsearch-response-instead-of-tabify/229815/4 "2020-05-26T13:26:49Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.