Update Journey Monitoring documentation to support partial DEM customers - #39210
Open
arti-arutiunov wants to merge 1 commit into
Open
Update Journey Monitoring documentation to support partial DEM customers#39210arti-arutiunov wants to merge 1 commit into
arti-arutiunov wants to merge 1 commit into
Conversation
Contributor
Preview links (active after the
|
janine-c
reviewed
Aug 14, 2026
janine-c
left a comment
janine-c
left a comment
Contributor
There was a problem hiding this comment.
Looks great! Just wanted to fix what I think might have been a typo, and then we'll be ready to rock for this one 🙂
| ## Prerequisites | ||
|
|
||
| Journey Monitoring requires the following products for frontend applications, each contributing different data to your journeys: | ||
| Journey Monitoring requires at **least one** of the following products to be enabled in frontend applications, each contributing different data to your journeys: |
Contributor
There was a problem hiding this comment.
Suggested change
| Journey Monitoring requires at **least one** of the following products to be enabled in frontend applications, each contributing different data to your journeys: | |
| Journey Monitoring requires **at least one** of the following products to be enabled in frontend applications, each contributing different data to your journeys: |
| The **Journey Monitoring map** displays all created and suggested journeys in a frontend application. Each tile in the map displays metrics on a journey's volume and conversion rate. If the journey has at least one Synthetic test defined, the tile also displays the journey's [Synthetic test suite][1] uptime metric. | ||
|
|
||
| <div class="alert alert-danger"><p>Only frontend applications that are instrumented with RUM without Limits, Synthetic Monitoring & Testing, and Product Analytics are eligible for Journey Monitoring.</p></div> | ||
| <div class="alert alert-danger"><p>Only frontend applications that are instrumented with RUM without Limits pr Synthetic Monitoring & Testing or Product Analytics are eligible for Journey Monitoring.</p></div> |
Contributor
There was a problem hiding this comment.
Suggested change
| <div class="alert alert-danger"><p>Only frontend applications that are instrumented with RUM without Limits pr Synthetic Monitoring & Testing or Product Analytics are eligible for Journey Monitoring.</p></div> | |
| <div class="alert alert-danger"><p>Only frontend applications that are instrumented with RUM without Limits, Synthetic Monitoring & Testing, or Product Analytics are eligible for Journey Monitoring.</p></div> |
Looks like this was a typo? I think this should cover it
jhgilbert
added
the
astro-reorg-no-conflicts
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
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.AI assistance
Additional notes