Add OpenTelemetry RUM data exploration section to documentation#5314
Open
alexandra5000 wants to merge 2 commits intoelastic:mainfrom
Open
Add OpenTelemetry RUM data exploration section to documentation#5314alexandra5000 wants to merge 2 commits intoelastic:mainfrom
alexandra5000 wants to merge 2 commits intoelastic:mainfrom
Conversation
- Introduced new sections on exploring OpenTelemetry RUM data in Kibana, including available views. - Added instructions for confirming data ingestion and noted limitations regarding OpenTelemetry RUM data visibility.
Contributor
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Contributor
🔍 Preview links for changed docs |
Contributor
Author
|
@david-luna would you mind reviewing this? 🙏 Issue for context: #4421 |
david-luna
requested changes
Mar 6, 2026
| You can explore OpenTelemetry RUM data in these {{kib}} experiences: | ||
|
|
||
| - **{{product.apm}} service inventory** | ||
| Browser apps that generate traces appear in the {{product.apm}} service inventory. You can view service details, open distributed traces, and explore end-to-end traces that include browser spans. |
Member
There was a problem hiding this comment.
[optional] for completeness you can mention the names displayed in the list correspond to the service.name resource attribute defined when instrumenting the app (L78)
| OpenTelemetry RUM traces are integrated with Elastic distributed tracing. Analyze request flows across browser and backend services in a single trace view. | ||
|
|
||
| - **Discover** | ||
| RUM events and metrics are indexed in {{es}}. In **Discover** you can inspect raw events, run exploratory queries, apply filters, and verify ingestion. You can also query browser Web Vitals (for example, `browser.web_vital` events) when they are emitted. However, there is no dedicated Web Vitals UI for OpenTelemetry RUM. |
Member
There was a problem hiding this comment.
[suggestion] the instrumentation code above does not include web vitals instrumentation. An implementation was added in open-telemetry/opentelemetry-browser#145 bt the package is not available yet.
Suggested change
| RUM events and metrics are indexed in {{es}}. In **Discover** you can inspect raw events, run exploratory queries, apply filters, and verify ingestion. You can also query browser Web Vitals (for example, `browser.web_vital` events) when they are emitted. However, there is no dedicated Web Vitals UI for OpenTelemetry RUM. | |
| RUM events and metrics are indexed in {{es}}. In **Discover** you can inspect raw events, run exploratory queries, apply filters, and verify ingestion. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a new Explore your data in KIbana section to the OpenTelemetry for RUM page so users know where and how to view OpenTelemetry RUM data after ingestion. The section also clarifies where OTEL RUM data does not appear and how to confirm ingestion.
Closes #4421
Generative AI disclosure
To help us ensure compliance with the Elastic open source and documentation guidelines, please answer the following:
Tool(s) and model(s) used: Composer 1.5