Having just upgraded our Elastic Cloud cluster from 7.12.1 to 7.13.0 we've found that
GET _nodes/stats now includes a fairly large chunk of data about "clients" which wasn't present before. This could be useful, but I'm not sure if it needs to be included by default? It's pretty hefty!
I believe the related issue from the release notes is Show Connected Clients API · Issue #61609 · elastic/elasticsearch · GitHub.
For us, this broke our integration with the justwatch/elasticsearch-exporter (which we use to make ElasticSearch stats Prometheus scrapable).
I can see that this can be disabled via the
http.client_stats.enabled cluster setting, but wonder if the default ought to be false, rather than true?
Further to this, using the
http.client_stats.enabled does remove the heavy response , but it doesn't fix my parsing problem because the
http part of the response still includes an empty array
I think you'll need to take this up with the folks responsible for the parsing code you're using. Adding fields to a response isn't considered a breaking change, we expect clients to ignore fields they don't recognise.
Thanks David. That’s a totally fair design assumption.
Sadly the exporter we’re using seems to have fallen out of regular maintenance some time ago, so I guess it was inevitable something like this would arise eventually. Will investigate what can be done though.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.