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

Changing uptime metric_type from counter to gauge across all packages for consistent mapping #7538

Open
ritalwar opened this issue Aug 25, 2023 · 1 comment

Comments

@ritalwar
Copy link
Contributor

There was a big discussion about how to categorize the uptime metric in the Windows package i.e whether it should be classified as a "gauge" or a "counter."

Even though uptime usually acts like a counter by going up over time, the discussion considered "temporality." After talking it through, everyone agreed that no matter if we're using "delta" or "cumulative" temporality settings, we should always treat uptime consistently and decided that uptime should never be reported as a "delta." So, labeled uptime as a "gauge." in Windows package.

While uptime is reported as a gauge in many packages, there are a few where it's reported as a counter. Therefore, we should update the current integrations to maintain a consistent mapping. Here's a list of packages that currently use uptime as a counter and need updates:

  • Apache
  • Elastic Package Registry
  • System (uptime datastream)
  • AWS (RDS)
@constanca-m
Copy link
Contributor

There is a related issue on delta metrics: elastic/elasticsearch#98171.

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

2 participants