-
Notifications
You must be signed in to change notification settings - Fork 889
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
Metric aggregation env variables are only for OTLP Exporter #4248
Comments
I think it is better to have the Moreover, the current env vars are stable. Therefore, I would rather propose defining equivalent env vars for other exporters than removing |
@cijothomas which other metric exporters are you wanting to define this for? |
For example, stdout - https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk_exporters/stdout.md There are also other exporters not part of the spec, that won't be able to leverage this env variable today as its tied to OTLP Exporter. |
does it make sense to look at this proposal under declarative configuration (instead of introducing any new env vars)? |
What are you trying to achieve?
Trying to influence Metric aggregation temporality, aggregation for histograms when using non-otlp exporting.
What did you expect to see?
A MeterProvider/MetricReader env variable to control the same.
However, the existing env variables are tied to OTLP Exporter only, and does not work when other exporting is used:
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk_exporters/otlp.md#additional-environment-variable-configuration
I think these variables should be respected by the SDK (after changing the name to remove "OTLP" from them).
The text was updated successfully, but these errors were encountered: