-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
document breaking change in metric names for prometheus exporter #12500
document breaking change in metric names for prometheus exporter #12500
Conversation
Fixes open-telemetry#12458 Signed-off-by: Alex Boten <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #12500 +/- ##
==========================================
- Coverage 92.16% 92.00% -0.17%
==========================================
Files 465 469 +4
Lines 25201 25355 +154
==========================================
+ Hits 23226 23327 +101
- Misses 1576 1619 +43
- Partials 399 409 +10 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Alex Boten <[email protected]>
|
||
The change to update the internal telemetry to use [otel-go config](https://pkg.go.dev/go.opentelemetry.io/contrib/config) can cause unexpected behaviour | ||
for end users. This change is caused by the default values in `config` being different from what the Collector has used in previous versions. The | ||
following changes can occur when users configure their `service::telemetry::metrics::readers`: |
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.
QQ: does it mean as long as you don't explicitly configure readers
you won't run into this? e.g. if I just have
service:
telemetry:
metrics:
level: detailed
the behavior of this should be the same in all versions, right?
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.
Yes, I think it worth mentioning that the breaking change only affects user how customized the prometheus reader in any way. The default behavior is the same
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.
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.
LGTM
Fixes #12458