-
Notifications
You must be signed in to change notification settings - Fork 20
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
Additional Prometheus exporter configuration options #59
Comments
Merged
3 tasks
carlosalberto
pushed a commit
to open-telemetry/opentelemetry-specification
that referenced
this issue
Dec 13, 2023
## Changes The suffix for types and units can be optionally disabled in Prometheus exporters. This PR captures these configuration options to allow them to then be captured by the OpenTelemetry Configuration as well. * [x] Related issues open-telemetry/opentelemetry-configuration#59
3 tasks
I know we've made some progress on this.. are there any important prometheus properties which still aren't part of the schema? As of now we have:
|
I believe all the necessary options have been added. I'll open follow up issues for any individual configurations if that's not the case. |
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this issue
Oct 31, 2024
## Changes The suffix for types and units can be optionally disabled in Prometheus exporters. This PR captures these configuration options to allow them to then be captured by the OpenTelemetry Configuration as well. * [x] Related issues open-telemetry/opentelemetry-configuration#59
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Prometheus exporter in Go exposes certain options that are necessary to be able to move forward with supporting configuration in the OpenTelemetry collector. These options are listed here: https://github.com/open-telemetry/opentelemetry-go/blob/main/exporters/prometheus/config.go
The question I have is whether we should add options for these in the config schema.
The text was updated successfully, but these errors were encountered: