Hello, is anyone else running ES 5.2 had an issue after 4.2 upgrade? After grafana upgrade all looks fine, until editing any chart query at which point the lucene query seems to break and the chart displays every single JSON key . Have I had a failed upgrade or is this a genera issue? Cheers, S…

We have had no reports of any breaking change yet.

Thanks for your reply, Very strange, I don’t appear to be able to edit any query, The charts look great until I attempt to edit the query. I’ll snapshot back to previous release and look at it again later. Best Regards Simon

If you do please include query sent to ES and response. And any js errors (chrome dev tools console).

I am seeing this also, I reverted back to 4.1 and it works fine. Not sure how to get grafana to show the queries it’s sending to elasticsearch so I can see what broke when using 4.2 with es5.2

here is a guide for how to troubleshoot / investigate query issues (and see raw query sent and response): [image] How to troubleshoot metric query issues How To If you get a panel query error or not seeing the data you expect to see the most important thing to do is view…

Thanks for that, I’ll find some time next week to debug

I’ve found the problem, it’s Min Doc Count - which I think is new? After upgrade Min Doc Count is 0 which seems to cause everything to be matched in a terms group by If I set it to 1, all is well. Thanks for your help.

I think you should consider setting default min_doc_count from default 0 to 1 By using 0 you’re overriding the ES default of 1 and causing terms to return that don’t match the query, and it breaks charts from previous release https://www.elastic.co/guide/en/elasticsearch/reference/current/search-a…

The problem with min_doc_count 1 is that it makes it impossible for Grafana to identify regions of missing data, there can be no gaps in the graphs in this case, so if you service goes down or stops sending data it’s going to be harder to see. Buckets returned when min doc count is 0 are null, so s…

I see your point. It may be my particular case, where I do a query like this to get my NGINX data: state.plugin_service_description:NGINX AND pfdta.metric_label:Active Then do a terms group by on hosts to show all the hosts, then group by date histogram; it returns a load of hosts that are not NGI…

Upgrade 4.2 issue ES 5.2

Grafana Elasticsearch

torkel March 24, 2017, 7:40pm 6

here is a guide for how to troubleshoot / investigate query issues (and see raw query sent and response):

Topic		Replies	Views
ES patched to 5.6 => some visualization is not shown Elasticsearch	7	1376	November 1, 2017
Elasticsearch Query in Grafana Grafana	2	5334	August 19, 2021
Grafana Raw Document metric not working for ElasticSearch v6 Elasticsearch	3	1643	August 10, 2018
Can't query elasticsearch data source from grafana	1	6441	June 7, 2017
Please, delete this thread Elasticsearch	1	601	September 8, 2017

Upgrade 4.2 issue ES 5.2

Related topics