-
Notifications
You must be signed in to change notification settings - Fork 35
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
Export cluster node name #161
Comments
Hey @steffenv-msft, |
If you're worried about determinability: Export a metric that checks if connection to the cluster endpoint is possible and attach the basic CIB options (cluster name, cluster-infrastructure, etc.) to it as labels. The only issue you'd walk into is that you'd have to parse the XML when the endpoint's actually down. |
The cluster node name should be available in the data exported on the endpoint to help identifying them in later analytics steps.
If connecting to the endpoints i.e. by IP address (http://IP:9664/metrics), it's currently impossible to correlate data imported to analytic data sources, unless there is a (manual) mapping somewhere available to the analytical data source also.
Ideally the cluster name can be made available as well.
The information is available from ". crm_node --name"
A simple approach could be to export as some kind of meta-data:
'# TYPE meta_data
meta_data{node="cluster node name",cluster="cluster name"} 1
or
'# TYPE meta_data
meta_data{node="cluster node name"} 1
meta_data{cluster="cluster name"} 1
The text was updated successfully, but these errors were encountered: