Repository navigation
Update RUM Operations docs with journey links and general content updates - #40378
Open
arti-arutiunov wants to merge 1 commit into
Open
arti-arutiunov wants to merge 1 commit into
arti-arutiunov wants to merge 1 commit into
Conversation
Contributor
Preview links (active after the
|
estherk15
reviewed
Oct 2, 2026
estherk15
left a comment
estherk15
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for the update, can you take another look at the images? Deleting images can lead to cacheing issues with our translated docs, so we recommend adding new images with unique filenames instead of writing over existing files.
|
|
||
| - `operation.name`, defined on the client side | ||
| - `operation.status`, either success or failure | ||
| - `operation.failure_reason`, either error, abandoned, or other |
Collaborator
There was a problem hiding this comment.
Suggested change
| - `operation.failure_reason`, either error, abandoned, or other | |
| - `operation.failure_reason`, error, abandoned, or other |
| - `operation.status`, either success or failure | ||
| - `operation.failure_reason`, either error, abandoned, or other | ||
|
|
||
| Use these metrics to create [metric monitors][22] and availability or latency SLOs for RUM operations. For recommended queries, thresholds, and examples, see [Best Practices for Creating SLOs for RUM Operations][23]. |
Collaborator
There was a problem hiding this comment.
Suggested change
| Use these metrics to create [metric monitors][22] and availability or latency SLOs for RUM operations. For recommended queries, thresholds, and examples, see [Best Practices for Creating SLOs for RUM Operations][23]. | |
| Use these metrics to create [metric monitors][22] and availability or latency Service Level Objectives (SLO) for RUM operations. For recommended queries, thresholds, and examples, see [Best Practices for Creating SLOs for RUM Operations][23]. |
| The table lists additional example journeys and their associated operations by industry. | ||
|
|
||
| | Industry | Journey | Journey operations | | ||
| | Industry | Journey | Operations | |
Collaborator
There was a problem hiding this comment.
Suggested change
| | Industry | Journey | Operations | | |
| | Industry | Journey | Operations | |
Collaborator
There was a problem hiding this comment.
Can you re-add the deleted images and rename the new images with a unique file name? Crop out the app menu bar if it's not impacted.
janakkar
approved these changes
Oct 6, 2026
|
|
||
| Each RUM operation generates a RUM event within its associated RUM session. An operation event can span multiple RUM views. | ||
|
|
||
| Query operation events from retained sessions in the [RUM Session Explorer][20] to investigate operation performance and failures. Operation events include these attributes: |
There was a problem hiding this comment.
may be good to mention that these are on top of the usual RUM event attributes, especially country, browser, service etc.
| - Engineering teams use **operations** to monitor and minimize technical failures that impact key moments in the journey. | ||
|
|
||
| For example, the checkout experience of an ecommerce platform is a journey. Within it, operations might include entering payment details, saving a payment method, and completing a purchase. After you create operations, Datadog RUM measures each operation's performance, including execution volume, completion rate, and failure rate. Measuring operations' health enables you to identify exactly when and why users may not convert in your journey. | ||
| For example, the checkout experience of an ecommerce platform is a journey. Its operations might include entering payment details, saving a payment method, and completing a purchase. Monitoring the health of these operations helps you identify when and why users do not complete the checkout journey. |
There was a problem hiding this comment.
maybe mention the loading of the checkout form
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.
What does this PR do? What is the motivation?
Merge readiness
AI assistance
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.Additional notes