[consul] more accurate nodes_* and services_* gauges #2130
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a rebased and slightly modified version of #2018 . It queries for cluster status via the
/v1/health/service/<service>
endpoint, which allows us to split the coarse-grainedconsul.catalog.nodes_up
andconsul.catalog.services_up
metrics into the followingconsul.catalog.nodes_passing
tagged byconsul_service_id
consul.catalog.nodes_warning
tagged byconsul_service_id
consul.catalog.nodes_critical
tagged byconsul_service_id
consul.catalog.services_passing
tagged byconsul_node_id
consul.catalog.services_warning
tagged byconsul_node_id
consul.catalog.services_critical
tagged byconsul_node_id
The
consul.catalog.nodes_up
andconsul.catalog.services_up
metrics are preserved with their original values, but will likely be removed or renamed in a future version of the check.Additionally
consul.check
service checks are now tagged byconsul_service_id
rather thanservice-id
to keep consistent with theconsul.catalog.*
tagging schemeTODOs:
consul.catalog.services_*
functionalitycc @mtougeron