You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i'm using the elastic-exporter to fetch data from our elastic.co clusters.
it used to work properly but suddenly i see a lot of errors on the exporter log: level=warn ts=2020-09-01T16:07:17.58499204Z caller=nodes.go:1865 msg="failed to fetch and decode node stats" err="HTTP Request failed with code 400"
when looking on the exporter metrics as http://localhost:9114 i dont see any metrics of nodes (such as elasticsearch_indices_indexing_index_total).
what can be the reason for this annoying error?
the exporter command on the deployment looks like the following
Hi
i'm using the elastic-exporter to fetch data from our elastic.co clusters.
it used to work properly but suddenly i see a lot of errors on the exporter log:
level=warn ts=2020-09-01T16:07:17.58499204Z caller=nodes.go:1865 msg="failed to fetch and decode node stats" err="HTTP Request failed with code 400"
when looking on the exporter metrics as http://localhost:9114 i dont see any metrics of nodes (such as elasticsearch_indices_indexing_index_total).
what can be the reason for this annoying error?
the exporter command on the deployment looks like the following
both staging and production clusters are 7.7.1.
staging cluster works as usual and we see all metrics, while prod not.
this 400 error can be related to overhead on the ES side?
how can i investigate it further?
10x
The text was updated successfully, but these errors were encountered: