-
Notifications
You must be signed in to change notification settings - Fork 59
Create placeholder for metrics common configuration #943
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
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #943 +/- ##
==========================================
+ Coverage 55.83% 56.27% +0.44%
==========================================
Files 255 255
Lines 22177 22180 +3
==========================================
+ Hits 12382 12482 +100
+ Misses 8956 8852 -104
- Partials 839 846 +7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| otel_traces_export: | ||
| endpoint: http://jaeger:4318 | ||
| meter_provider: | ||
| obi_features: |
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.
why do we call them obi_features, instead of features?
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.
With the new changes, this is already: metrics > features
…nstrumentation into meter-provider
grcevski
left a comment
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!
In preparation:
otel_metric_export > featuresto a commonmetrics > features, and deprecate itprometheus > featurestometrics > features, and deprecate itopentelemetry.iodocs as soon as the new property is accepted/agreed.The reason to move the features specification to a common section is because in the next PRs, we will allow a declarative per-service metric features definition. Having different metric features per export endpoint adds a lot of complexity to the code.