-
Notifications
You must be signed in to change notification settings - Fork 896
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
Make periodic exporting MetricReader env vars stable #2658
Conversation
PTAL @open-telemetry/java-instrumentation-maintainers @open-telemetry/python-maintainers @open-telemetry/php-approvers @open-telemetry/wg-prometheus |
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.
The OTEL_METRICS_EXEMPLAR_FILTER
is still in very early stage and should remain as Experimental, consider marking the "Metrics SDK Configuration" status as Mixed, and make the "Periodic exporting MetricReader" section Stable.
In addition, consider making an update in /~https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md#environment-variables. Doesn't have to be in this PR though.
What
Mark
OTEL_METRIC_EXPORT_INTERVAL
,OTEL_METRIC_EXPORT_TIMEOUT
environment variables as stable.Why
I think this change is representing the current state as all of these env vars are already implemented in OTel PHP, OTel Python, and partially by OTel Java.
See:
OTEL_METRIC_EXPORT_INTERVAL
usageOTEL_METRIC_EXPORT_TIMEOUT
usageCreated because of: open-telemetry/opentelemetry-dotnet#3424