-
Notifications
You must be signed in to change notification settings - Fork 225
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
fix: remove zero count metrics from registry #2163
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪 |
@@ -144,7 +159,7 @@ test('does not include breakdown when not sampling', t => { | |||
|
|||
const { metricsets } = data | |||
|
|||
assertMetricSet(t, 'transaction', metricsets, { | |||
assertMetricSet(t, 'transaction not sampling', metricsets, { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously this test asserted that transaction.breakdown.count
was reported. However, with the new behavior the transaction.breakdown.count
metric is no longer reported in this specific scenario because its count is zero.
jenkins run the tests please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just the changelog nit. Otherwise looks perfect.
CHANGELOG.asciidoc
Outdated
* The agent will no longer report couting metrics with a value of zero, and will | ||
remove these metrics from the registry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- s/couting/counting/
- Issue link please.
* feat: no longer sends counting metrics with a count of zero and removes them from the metrics cache/registry Closes: elastic#1977
Closes #1977
Checklist