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 Integration Metric Naming #16953

Open
reskin89 opened this issue Feb 23, 2024 · 0 comments
Open

Consul Integration Metric Naming #16953

reskin89 opened this issue Feb 23, 2024 · 0 comments

Comments

@reskin89
Copy link

Issue

I am seeing metrics in datadog for consul.raft.heartbeat also including what seems to be a heartbeat ID as part of the metric, for example:

consul.raft.replication.heartbeat.07914c80_085b_bfa1_c1a3_4fae883f18e7.avg

This, according to the docs should just be: consul.raft.replication.heartbeat.avg and so on with median, sum etc.

This makes it nearly impossible to make alerts or dashboards with this metric as it has a great deal of values.

This identification stamp (it is not a consul node id or anything of the sort) should most likely be a tag on the metric and not part of the metric name.

Additional environment details (Operating System, Cloud provider, etc):
AWS Amazon Linux 2

Steps to reproduce the issue:

  1. Run a datadog agent with consul integration
  2. Check the consul.raft.replication.heartbeat metrics that come in.

Describe the results you received:

I have a great deal of consul.raft.replication.heartbeat.SOMERANDOMID metrics, making it impossible to isolate that metric as a whole for my cluster

Describe the results you expected:

To have a single set of consul.raft.replication.heartbeat metrics that I can then filter by tag.

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

No branches or pull requests

1 participant