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

Make extention configuration OTEL familiar #25

Open
olegbespalov opened this issue Oct 11, 2024 · 0 comments
Open

Make extention configuration OTEL familiar #25

olegbespalov opened this issue Oct 11, 2024 · 0 comments

Comments

@olegbespalov
Copy link
Collaborator

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.

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.

@olegbespalov olegbespalov changed the title Make extention OTEL SDK friendly Make extention configuration OTEL familiar Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant