Splunk RUM metrics integration 🔗
Integrate with Splunk RUM so that you can automatically measure Web Vital metrics against your run results. Web vitals capture key metrics that affect user experience and assess the overall performance of your site. Many businesses rely on search engines for users to discover their sites. Google uses web vitals to determine page ranking.
Web vitals are made up of these metrics that measure user experience.
Metric name |
Description |
|---|---|
Largest contentful paint (LCP) |
Measures loading performance by capturing the render time of the largest image or text block visible within the viewport. |
Cumulative layout shift (CLS) |
Measures visual stability by capturing the sum of all individual layout shift scores for every unexpected layout shift that occurs during the entire lifespan of the page. A layout shift occurs any time a visible element changes its position from one rendered frame to the next. Fewer shifts are better for page stability. |
First input delay (FID) |
Measures the time from when a user first interacts with a web page to the time when the browser is able to respond to that interaction |
Total blocking time (TBT) |
TBT is collected from a synthetic test, while FID is collected from real user data and they both may be considered equivalent to each other since they measure the same metric: time taken by the page to become interactive and responsiveness to the user. |
Prerequisites 🔗
You need to instrument your browser application with Splunk RUM. See, Instrument browser-based web applications for Splunk RUM.
View web vitals for your run results 🔗
Navigate to the run results page for the test you’re interested in monitoring. The metrics panel for each run result lists web vitals, performance timing, and other metrics. Each web vital shows how your metrics compare to the acceptable range.
For example, this image shows the acceptable ranges for TBT. Select the flash light icon to open the sessions in Tag Spotlight in Splunk RUM. The visit count represents the number of users and synthetic tests that have interacted with the normalized URL specified in the test.
Compare latency of a test by run location 🔗
Web vitals are a great way of measuring if your tests are actually capturing the performance you expect. Suppose you want to compare the latency of your tests by run location. Open the run results of your test. In the metrics panel, select the filter icon to open the run location options dialog box.
Example 🔗
The site reliability engineering (SRE) team at the fictitious Buttercup Games company sets up tests to monitor the checkout workflow for their online store using an API test. For steps on how they setup their API test, see Scenario: Kai monitors API performance for a critical workflow. The SRE team wants to determine the health of the API test by run location. The data centers for Buttercup Games are in Johannesburg and the web vitals for the local tests reflect optimal performance.
Using the RUM integration, the SRE team can compared web vitals by global results and found that the LCP really lagged.
To investigate which regions are experiencing poor performance, the SRE team selects the RUM link to Tag Spotlight. The team sees that Mumbai has a large range of response times for LCP. The SRE team can apply Mumbai as a filter and explore individual user sessions to find if there are performance discrepancies in relation to the of type of browser, browser version, OS Version, App version and more.
See also 🔗
To learn more about:
Web Vitals, see https://web.dev/vitals/ in the Google developer documentation
What kind of use cases you can solve with Splunk RUM, see Scenarios for monitoring applications and services using Splunk RUM
Tag spotlight, see Error monitoring and crash aggregation in Tag spotlight