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
As pointed out in #24, how we currently define our default configuration makes it harder to use the output and confuses users familiar with OTEL SDK configuration.
The current approach was likely adopted to provide k6-specific configurability. However, it creates a divergence from standard OTEL practices, potentially confusing users familiar with OTEL SDK configuration.
Moving forward, we should consider:
Gradually aligning our custom variables with standard OTEL naming conventions.
Implementing a fallback mechanism where standard OTEL variables are checked if custom ones are not set.
Providing clear documentation on which standard OTEL variables are supported and which are superseded by custom configurations.
So, we must adjust our configuration and consider OTEL environment variables if they are defined. Still K6_OTEL_ will have priority.
Why?
Align with OTEL.
The text was updated successfully, but these errors were encountered:
olegbespalov
changed the title
Make extention OTEL SDK friendly
Make extention configuration OTEL familiar
Oct 11, 2024
What?
As pointed out in #24, how we currently define our default configuration makes it harder to use the output and confuses users familiar with OTEL SDK configuration.
So, we must adjust our configuration and consider OTEL environment variables if they are defined. Still
K6_OTEL_
will have priority.Why?
Align with OTEL.
The text was updated successfully, but these errors were encountered: