Skip to content

Commit 5404c32

Browse files
authored
Update docs/apm/real-user-monitoring/metrics.md
1 parent 984ea35 commit 5404c32

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/apm/real-user-monitoring/metrics.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,7 @@ These CWV KPIs are captured and displayed on Overview dashboards for Document Lo
127127
Currently, XHR metrics extraction in RUM is only supported for applications that use the `fetch` API to perform XHR calls. If your application uses `XMLHttpRequest`, metrics may not be collected at this time. A fix to support `XMLHttpRequest`-based calls is in progress and expected to roll out in mid 2025. We will update this page when that support becomes available.
128128
:::
129129

130-
An **XMLHttpRequest (XHR)** is a way for browsers to communicate with a backend server without reloading the page. For example, a page may use XHR to update a price ticker automatically or after clicking an Update Price button.
130+
An XMLHttpRequest (XHR) is a way for browsers to communicate with a backend server without reloading the page. For example, a page may use XHR to update a price ticker automatically or after clicking an "Update Price" button.
131131

132132
XHR is commonly used in *single-page applications* (SPAs), which load once and then handle all interactions without refreshing the page. These apps often generate multiple XHR requests—typically HTTP `POST` or `GET` calls—based on user actions.
133133

0 commit comments

Comments
 (0)