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

[APM] [OTel] Transaction and Span Flyout for OTel data #195788

Open
AlexanderWert opened this issue Oct 10, 2024 · 1 comment
Open

[APM] [OTel] Transaction and Span Flyout for OTel data #195788

AlexanderWert opened this issue Oct 10, 2024 · 1 comment
Labels
apm:opentelemetry APM UI - OTEL Work apm enhancement New value added to drive a business result OpenTelemetry Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team

Comments

@AlexanderWert
Copy link
Member

Span and Transaction Flyouts do not differentiate between classic APM data and OTel-native data.
The result is that it shows

  • all the fields (including aliases) that are then shown as duplicates
  • it does not differentiate between different categories of fields

Image

With OTel-native data we have the chance to create a more appealing experience for these flyouts by explicitly differentiating between attributes, resource attributes, scope attributes and OTLP native fields.

@AlexanderWert AlexanderWert added the Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team label Oct 10, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

@smith smith added enhancement New value added to drive a business result OpenTelemetry apm apm:opentelemetry APM UI - OTEL Work labels Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
apm:opentelemetry APM UI - OTEL Work apm enhancement New value added to drive a business result OpenTelemetry Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team
Projects
None yet
Development

No branches or pull requests

3 participants