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

Added mapping of experimental Otel telemetry.distro.name and version attributes #203

Merged
merged 7 commits into from
Mar 12, 2024

Conversation

JonasKunz
Copy link
Contributor

Closes #200 .

@JonasKunz JonasKunz requested a review from a team as a code owner January 24, 2024 13:20
@SylvainJuge
Copy link
Member

Once we will have "otel native" storage, those fields would be stored as top-level elements.

We will need to modify the UI to make use of those (for example to show a proper Elastic + Otel label on services where it's used), so if we can also store them as top-level elements that would provide a future-proof mapping in the UI.

This is the strategy that was used to add code.stacktrace in #177

@v1v v1v added safe-to-test Changes are safe to run in the CI and removed safe-to-test Changes are safe to run in the CI labels Feb 2, 2024
@v1v v1v added safe-to-test Changes are safe to run in the CI and removed safe-to-test Changes are safe to run in the CI labels Feb 2, 2024
input/otlp/metadata.go Show resolved Hide resolved
@kruskall kruskall merged commit 0e072ce into elastic:main Mar 12, 2024
5 checks passed
@JonasKunz JonasKunz deleted the otel-distro-agent-name branch April 5, 2024 09:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
safe-to-test Changes are safe to run in the CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Map new telemetry distro attributes to agent fields for OTel distros
4 participants