-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[otel-data] Add profiler_stack_trace_ids as counted_keyword to otel-data mappings #125608
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
[otel-data] Add profiler_stack_trace_ids as counted_keyword to otel-data mappings #125608
Conversation
Pinging @elastic/es-data-management (Team:Data Management) |
Are there already docs for |
Right - and maybe the PR itself: #101826 But I don't find normal docs either. |
As discussed in the overall issue, changed the field we map to |
…ata mappings (elastic#125608) * Add profiler_stack_trace_ids as counted_keyword to otel-data mappings * Change prefix for profiler_stack_trace_ids
…tion (#217020) Depends on elastic/elasticsearch#125608 # Summary `ELASTIC_PROFILER_STACK_TRACE_IDS` is introduced for OTel based data streams. The same information is stored in `TRANSACTION_PROFILER_STACK_TRACE_IDS` in the classic APM data streams. Prior to this PR apm<->profiling integration did not work for OTel SDKs. This PR adds handling for the new field name. <img width="1159" alt="Screenshot 2025-04-03 at 10 05 28" src="https://github.com/user-attachments/assets/ce3ad092-d4f4-4a16-843e-923c72938fe1" /> <img width="1772" alt="Screenshot 2025-04-03 at 10 05 40" src="https://github.com/user-attachments/assets/8b2682fe-6f2e-49a4-9995-d83997a05f02" /> --------- Co-authored-by: Greg Kalapos <[email protected]>
Adding mapping for profiling <-> traces integration for OTel data.
cc @rockdaboot