Skip to content
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

[consul] more accurate nodes_* and services_* gauges #2130

Merged
merged 6 commits into from
Dec 7, 2015
Merged

Conversation

talwai
Copy link
Contributor

@talwai talwai commented Dec 7, 2015

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-grained consul.catalog.nodes_up and consul.catalog.services_up metrics into the following

  • consul.catalog.nodes_passing tagged by consul_service_id
  • consul.catalog.nodes_warning tagged by consul_service_id
  • consul.catalog.nodes_critical tagged by consul_service_id
  • consul.catalog.services_passing tagged by consul_node_id
  • consul.catalog.services_warning tagged by consul_node_id
  • consul.catalog.services_critical tagged by consul_node_id

The consul.catalog.nodes_up and consul.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 by consul_service_id rather than service-id to keep consistent with the consul.catalog.* tagging scheme

TODOs:

  • Add tests for consul.catalog.services_* functionality

cc @mtougeron

@olivielpeau olivielpeau added this to the 5.6.3 milestone Dec 7, 2015
talwai added a commit that referenced this pull request Dec 7, 2015
[consul] more accurate nodes_* and services_* gauges
@talwai talwai merged commit 69512b8 into master Dec 7, 2015
@mtougeron
Copy link
Contributor

Ya, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants