You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: