-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect aerospike metrics export to prometheus with more than 1 node in aerospike cluster #2917
Comments
Can you add the output of |
Sure:
As you can see, prometheus_client output every time gives aerospike_node_objects metric from random aerospike host. |
I think we need to make the |
Needs fixed for both the @popov-ilya Are you interested in doing this? |
Unfortunately i don't have necessary skills for this. |
I'll copy my comment over from the PR:
So the fix doesn't provide the requested functionality of scraping a single node, if this is a problem then you can reopen this issue. |
Bug report
Relevant telegraf.conf:
System info:
Steps to reproduce:
telegraf -input-filter aerospike -output-filter prometheus_client config
telegraf --config telegraf.conf -test
curl 192.168.1.18:9126/metrics
. Do it few times.Expected behavior:
prometheus_client should provide aerospike metrics from the host where telegraf is running.
Actual behavior:
prometheus_client may provide metrics from any host in your aerospike cluster.
Additional info:
If you do telegraf -test, it will give you aerospike_node and aerospike_namespace X times, where X is the node count in your aerospike cluster. Then if you query prometheus_client output with curl on :9126/metrics you will get 1 set of metrics, which should be from the host where telegraf is running. But actually it gives you metrics from any of your aerospike hosts and host may change every collection interval. It results in a lot of spikes on dashboards even for metrics than didn't actually change.
In previous version 1.2.1 it always get metrics from the same one host, but it is not necessary the right host.
The text was updated successfully, but these errors were encountered: