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
Upgrading 5.41.1 to broke a number of our metrics. We're having a hard time tracking down exactly what happened, but something in 5.41.1 definitely caused some of our counter metrics to increase by an order of magnitude.
In the chart below, we deployed a PR where the only substantive change was upgrading from 5.40.0 to 5.41.1.
We're currently downgrading the version to confirm this is the cause.
Perhaps related, our count metrics in Datadog are now type=gauge.
Reproduction Code
This is our code to increment a metric.
exporttypeMetricTags=Partial<Record<MetricTag,string|number>>;exportfunctionincrement(namespace: MetricNamespace,metric: MetricName,amount: number,tags?: MetricTags,// Accept string | undefined to make it easier for the client){ddTracer.dogstatsd.increment(getStat(namespace,metric),amount,tags);}
Error Logs
No response
Tracer Config
No response
Operating System
No response
Bundling
Unsure
The text was updated successfully, but these errors were encountered:
Tracer Version(s)
5.41.1
Node.js Version(s)
22.14
Bug Report
Upgrading 5.41.1 to broke a number of our metrics. We're having a hard time tracking down exactly what happened, but something in 5.41.1 definitely caused some of our counter metrics to increase by an order of magnitude.
In the chart below, we deployed a PR where the only substantive change was upgrading from 5.40.0 to 5.41.1.
We're currently downgrading the version to confirm this is the cause.
Perhaps related, our count metrics in Datadog are now type=gauge.
Reproduction Code
This is our code to increment a metric.
Error Logs
No response
Tracer Config
No response
Operating System
No response
Bundling
Unsure
The text was updated successfully, but these errors were encountered: