Skip to content
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

Add config to skip attaching InstrumentationScopeInfo as labels #357

Closed
Noremac201 opened this issue Jul 9, 2024 · 0 comments · Fixed by #358
Closed

Add config to skip attaching InstrumentationScopeInfo as labels #357

Noremac201 opened this issue Jul 9, 2024 · 0 comments · Fixed by #358
Assignees
Labels
enhancement New feature or request

Comments

@Noremac201
Copy link

For some first-party Google Cloud metrics, there can be a need to export to publicy writable metrics directly. This can cause issues when attaching instrumentation scope info as labels, as this will be rejected by the createTimeSeries call if mismatched labels are found. There is currently no way to disable this on a config-based level, which means writing to 1P metrics is currently infeasible without a custom code change.

Example error:

WARNING: Exporter threw an Exception
com.google.api.gax.rpc.InvalidArgumentException: io.grpc.StatusRuntimeException:
 INVALID_ARGUMENT: One or more TimeSeries could not be written: Unrecognized metric 
labels: [instrumentation_source], [instrumentation_version]; 

This is a feature on some other exporters as well:

https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/blob/648a71ca81a051f32a3accc68c62f60c75469822/exporter/collector/config.go#L127

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
2 participants