You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the underlying problem you're trying to solve?
I would like the traces emitted by OPA to contain custom resource attributes that I provide. For example, service.namespace, which allows me to differentiate between the traces from multiple OPA instances.
Describe the ideal solution
Provide distributed_tracing.resource_attributes config, which accepts a list of key-value pairs, which are passed along to the OpenTelemetry SDK. Most OpenTelemetry SDKs do this via the OTEL_RESOURCE_ATTRIBUTES environment variable, and those would be passed to the tracer provider
This seems like a good addition. Updating the config to provide key-value pairs seems like a good approach. Feel free to contribute this feature if you'd like.
What is the underlying problem you're trying to solve?
I would like the traces emitted by OPA to contain custom resource attributes that I provide. For example,
service.namespace
, which allows me to differentiate between the traces from multiple OPA instances.Describe the ideal solution
Provide
distributed_tracing.resource_attributes
config, which accepts a list of key-value pairs, which are passed along to the OpenTelemetry SDK. Most OpenTelemetry SDKs do this via theOTEL_RESOURCE_ATTRIBUTES
environment variable, and those would be passed to the tracer providerDescribe a "Good Enough" solution
Using https://opentelemetry.io/docs/languages/go/resources/
resource.WithFromEnv()
inopa/internal/distributedtracing/distributedtracing.go
Line 102 in 291825e
Additional Context
The text was updated successfully, but these errors were encountered: