# Elasticsearch Visualization Search error with empty response
**URL:** https://discuss.elastic.co/t/elasticsearch-visualization-search-error-with-empty-response/270706
**Category:** Kibana
**Created:** [April 20, 2021, 1:10pm UTC](https://discuss.elastic.co/t/elasticsearch-visualization-search-error-with-empty-response/270706 "2021-04-20T13:10:12Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Kuo\_Hugo](https://discuss.elastic.co/u/Kuo_Hugo)
#### Post date: [April 20, 2021, 1:10pm UTC](https://discuss.elastic.co/t/elasticsearch-visualization-search-error-with-empty-response/270706/1 "2021-04-20T13:10:12Z")
The batch query for rendering a visualization from the search `programname:"proxy-server" AND status_int:[200 TO 299] and request_method:GET` . The search works fine even with 7days period. But the visualization as below always return error.
```auto
{"batch":[{"request":{"params":{"index":"logstash-*","body":{"aggs":{"2":{"significant_terms":{"field":"object.keyword","size":100}}},"size":0,"fields":[{"field":"@timestamp","format":"date_time"},{"field":"rsyslog.timestamp","format":"date_time"}],"script_fields":{},"stored_fields":["*"],"_source":{"excludes":[]},"query":{"bool":{"must":[{"query_string":{"query":"programname:\"proxy-server\" AND status_int:[200 TO 299] and request_method:GET","analyze_wildcard":true,"time_zone":"UTC"}}],"filter":[{"match_all":{}},{"range":{"rsyslog.timestamp":{"gte":"2021-04-20T09:01:03.889Z","lte":"2021-04-20T10:01:03.889Z","format":"strict_date_optional_time"}}}],"should":[],"must_not":[]}}},"preference":1618905798661}},"options":{}}]
```
Here's the [Elasticsearch stats](https://cloud.swiftstack.com/v1/AUTH_hugo/test/cluster_stats.txt)
- The ELK stack is deployed via helm chart in K8S.
- All nodes(pods) are in dlmr roles.
- The diskIO looks fine. There're more than 80 NMVEs.
- I'm trying to find the bottleneck but no luck. It seems the performance issue for me but not sure if it's from data node role. If yes, how to prove that?
- Is there any useful logs for this situation?
Thanks // Hugo
---
### Author:  [@devon.thomson](https://discuss.elastic.co/u/devon.thomson)
#### Post date: [April 20, 2021, 4:29pm UTC](https://discuss.elastic.co/t/elasticsearch-visualization-search-error-with-empty-response/270706/2 "2021-04-20T16:29:12Z")
Hi @Kuo_Hugo.
Which visualization type creates this request? Does the query work correctly in discover?
---
### Author:  [@Kuo\_Hugo](https://discuss.elastic.co/u/Kuo_Hugo)
#### Post date: [April 20, 2021, 5:55pm UTC](https://discuss.elastic.co/t/elasticsearch-visualization-search-error-with-empty-response/270706/3 "2021-04-20T17:55:38Z")
ELK version 8.0.0
It’s vertical bar.
 
Thx / Hugo
---
### Author:  [@devon.thomson](https://discuss.elastic.co/u/devon.thomson)
#### Post date: [April 20, 2021, 8:09pm UTC](https://discuss.elastic.co/t/elasticsearch-visualization-search-error-with-empty-response/270706/4 "2021-04-20T20:09:40Z")
The 8.0.0 snapshot is unsupported, so there may be some issues present in bsearch that prevent the error from being reported properly and result in an empty response. Have you tried this in an older version?
Additionally, you can check the server output for any errors.
---
### Author:  [@Kuo\_Hugo](https://discuss.elastic.co/u/Kuo_Hugo)
#### Post date: [April 21, 2021, 11:38am UTC](https://discuss.elastic.co/t/elasticsearch-visualization-search-error-with-empty-response/270706/5 "2021-04-21T11:38:03Z")
Thanks for the suggestion. The Significant Terms aggregation consumes all the resources. We decided to use Terms instead. And it works for us in this case.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 19, 2021, 11:38am UTC](https://discuss.elastic.co/t/elasticsearch-visualization-search-error-with-empty-response/270706/6 "2021-05-19T11:38:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.