-
Notifications
You must be signed in to change notification settings - Fork 359
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
Traverse the Elasticsearch JSON tree to automatically include any numeric values #269
Conversation
…d don't change the metric names
Can you attach a list of the new metrics and tags? |
Here are two files showing example output, one for an elasticsearch client node and an elasticsearch master node. |
I like this collector, let me think about a way to have it alongside the previous one and issue deprecation warnings. |
We use this in production against 1.7.1 and also tested in dev agaist 2.2.0. It fails against AWS es 1.5.1 but only because Amazon denies requests to /_cluster. It's possible to write some testing for those responses and handle them gracefully at some point. |
Pardon the jamming, we've open-sourced some more fixes to allow threading for multiple hosts (we monitor up to 10 nodes with one collector, bringing run time from 3s to .5s). We also include byindex stats for bytes and docs (per index) from the master. Attached is a revised copy of the master's metric outputs. Client/data nodes are unchanged. |
Would it be possible to get the plugin names here? I would be concerned that plugin 0 wasn't the same plugin across multiple instances. elasticsearch.cluster.nodes.plugins.0.site 1455667836 1 node=esmasterlogs1 cluster=eslogs |
This was introduced in I think it is a minor cosmetic issue since these are plugin booleans. I think there are several scenarios:
Option 1 has the least risks and easiest to implement I'll mull over options 2 or 3 to see if this is easy. |
Here's the json that causes it. Not a lot of good metrics in there. Interesting data but not metrics.
|
Updated to remove bool metrics. |
There are a number of metrics that are not exported by the current code. Also, metrics are renamed and slightly differ against the elastic search values. This code traverses the output of /_nodes/_local/stats and pulls every numeric metric out without changes.
Plus, less code is better code. :)
One serious caveat: the metrics names will be different so this is a breaking change.