elasticsearch_exporter: Elasticsearch 7.13 Breaking Metrics
Elasticsearch 7.13 appears to have removed several key metrics around cluster disk storage etc.
This means metrics like elasticsearch_filesystem_data_size_bytes
are no longer present.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 15
- Comments: 20 (1 by maintainers)
Commits related to this issue
- test: refactor TestNodesStats As per #419, this functionality is failing for elasticsearch version 7.13+ due to a breaking change in the response from elasticsearch. This adds some test fixtures for ... — committed to sysadmind/elasticsearch_exporter by sysadmind 3 years ago
- test: refactor TestNodesStats As per #419, this functionality is failing for elasticsearch version 7.13+ due to a breaking change in the response from elasticsearch. This adds some test fixtures for ... — committed to transferwise/elasticsearch_exporter by sysadmind 3 years ago
- test: refactor TestNodesStats As per #419, this functionality is failing for elasticsearch version 7.13+ due to a breaking change in the response from elasticsearch. This adds some test fixtures for ... — committed to jnadler/elasticsearch_exporter by sysadmind 3 years ago
I think the problem is that they have added info on each HTTP client to HTTP stats and this breaks the nodes_response collector.
I think this is a fast solution but I don’t know how to export the new metrics. I’m using this branch for building because the original one is broken.
diff.txt
Using elasticsearch-exporter:master version worked for me too. Can somebody comment on when the actual version is getting released, we use that (example: 1.2.0) in our images.
Same here, error log:
caller=nodes.go:1851 msg=“failed to fetch and decode node stats” err=“json: cannot unmarshal array into Go struct field NodeStatsNodeResponse.http of type int”
My bild is working ok 😃 Are you using fix-build-go-mod branch from https://github.com/repl-mike-roest/elasticsearch_exporter for building?