-
Notifications
You must be signed in to change notification settings - Fork 223
DOCS-895 - Remove XHR metrics from RUM docs #5423
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -58,7 +58,7 @@ The **RUM Overview** dashboards (**Application**, **Service**, **Service with En | |||
|
|||
Use these dashboards to: | |||
* Analyze load and paint timings for page document loads by application, service, or action. | |||
* View information about core web vitals, XHR processing times/errors, and log errors. | |||
* View information about [core web vitals, XHR processing times/errors, and log errors](/docs/apm/real-user-monitoring/metrics/#xhr-monitoring-metrics). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link is giving 404. We should change it to following.
* View information about [core web vitals, XHR processing times/errors, and log errors](/docs/apm/real-user-monitoring/metrics/#xhr-monitoring-metrics). | |
* View information about [core web vitals, XHR processing times/errors, and log errors](/docs/apm/real-user-monitoring/metrics.md#xhr-monitoring-metrics). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -78,7 +78,7 @@ The **RUM - TopN - Application** and **RUM - TopN - Application Service** dashbo | |||
Use these dashboards to: | |||
* Find out top N browsers, operating systems, and geolocations by load or requests. | |||
* Understand the slowest and fastest browsers from a rendering perspective or geographical locations from a network perspective. | |||
* Understand XHR and log errors your users are experiencing. | |||
* Understand [XHR and log errors](/docs/apm/real-user-monitoring/metrics/#xhr-monitoring-metrics) your users are experiencing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link is correct; you'd need to pull it in locally and test
@@ -123,11 +123,15 @@ These CWV KPIs are captured and displayed on Overview dashboards for Document Lo | |||
|
|||
## XHR monitoring metrics | |||
|
|||
An XML HTTP Request (XHR) is a form of communication between the browser and the application backend without reloading the page. A typical example is when a page needs to update a price ticker automatically or after pressing the “update price” button next to it. | |||
:::note |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes - to preview the correct formatting, you'd need to pull it in locally.
Here's what it looks like in localhost
Purpose of this pull request
Remove XHR metrics from RUM docs
Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-895