Documentation forSolarWinds Observability SaaS

Digital Experience metrics

Depending on the options selected when Adding a website entity, data available for website entities may include synthetic availability and real user monitoring metrics. Synthetic availability monitoring is available for added URI entities. See Real user monitoring and Synthetic monitoring for how these metrics are collected.

Many of the collected metrics from website and URI entities are displayed as widgets in SolarWinds Observability explorers; additional metrics may be collected and available in the Metrics Explorer. You can also create an alert for when an entity's metric value moves out of a specific range. See Entities in SolarWinds Observability SaaS for information about entity types in SolarWinds Observability SaaS.

Page Speed metrics

The following table lists some of the metrics collected for these entities. To see the website or URI endpoint's availability metrics in the Metrics Explorer, type synthetics. in the search box.

Metric Units Description
synthetics.attempts Count Value representing the sum of all (successful and unsuccessful) page loads for a selected time period. Used to calculate the success and error rate.
synthetics.availability Percent (%)

Overall Availability, Availability History. Represents if a website is available or unavailable.

Found in: Metrics Explorer, Entity Explorer (Availability tab)

At the end of April, the synthetics.availability metric will no longer be available. You should begin transitioning your alerts, custom dashboards, and API data requests to use the composite.synthetics.availability metric. Instead of calculating availability as a percentage based on the proportion of successful tests, the new composite.synthetics.availability metric calculates availability based on the total amount of time a website or URI entity is available and acts as a 1:1 replacement for the requirements and use cases of synthetics.availability.
synthetics.errors Count The total downtime for the entity during the specified time range.
synthetics.error_rate Percent (%) Error Rate. Percentage of the tests that ran during the specified time period and failed. A test fails if an error prevents the website(s) from loading.

Found in: Metrics Explorer, Entity Explorer, DEM area overview

synthetics.pagespeed.cumulative_layout_shift   Measures the sum of all unexpected layout shifts during the page life cycle.
synthetics.pagespeed.diagnostics.content_size By Measures space used by content types (scripts, styles, images) post-compression, highlighting optimization areas.
synthetics.pagespeed.diagnostics.content_size.total   Total size of all content types (scripts, styles, images) after compression, indicating overall data transfer.
synthetics.pagespeed.diagnostics.network.latency Milliseconds (ms) Measures round-trip time for data to the server, reflecting backend and network response speed.
synthetics.pagespeed.diagnostics.network.transfer By Measures total bytes sent over the network, indicating data transfer and compression efficiency.
synthetics.pagespeed.diagnostics.requests   Counts and categorizes network requests (scripts, styles, fonts, images), revealing webpage complexity and loading behavior.
synthetics.pagespeed.diagnostics.requests.total   Total number of requests made by the page, indicating overall complexity and resource usage.
synthetics.pagespeed.diagnostics.tasks   Breaks down main thread task durations, useful for identifying performance issues like jank.
synthetics.pagespeed.first_contentful_paint Milliseconds (ms) Marks the time at which the first text or image is painted.
synthetics.pagespeed.first_meaningful_paint Milliseconds (ms) Measures when the primary content of a page is visible.
synthetics.pagespeed.interaction_to_next_paint Milliseconds (ms) Measures the time from user interaction to the next visual update.
synthetics.pagespeed.largest_contentful_paint Milliseconds (ms) Marks the time at which the largest text or image is painted.
synthetics.pagespeed.max_potential_first_input_delay    
synthetics.pagespeed.page_size By Total size of all resources loaded by the page.
synthetics.pagespeed.performance.opportunity   Counts performance opportunities, indicating potential improvements for faster load times.
synthetics.pagespeed.performance.score   A Lighthouse score reflecting overall performance based on key metrics like FCP and LCP.
synthetics.pagespeed.response.time    
synthetics.pagespeed.speed_index Milliseconds (ms) Shows how quickly the contents of a page are visually populated.
synthetics.pagespeed.timeline Milliseconds (ms) Displays key browser events (Time to First Byte, DOM Content Loaded) over time, visualizing loading sequences.
synthetics.pagespeed.total_blocking_time Milliseconds (ms) Total time that the main thread was blocked preventing user input during load.

Synthetic availability metrics

The following table lists some of the metrics collected for these entities. To see the website or URI endpoint's availability metrics in the Metrics Explorer, type synthetics. in the search box.

Metric Units Description
composite.synthetics.availability Percent (%) Overall Availability, Availability History. Represents if a website is available or unavailable.

 

Found in: Metrics Explorer, Entity Explorer (Availability tab)

composite.synthetics.status.downtime.count Count

Value representing the number of times the website entity was down in a given time range.

For example, if the entity was down the entirety of the time range, the count would be 1.

composite.synthetics.status.downtime.total Seconds (s) The total downtime for the entity during the specified time range.
synthetics.attempts Count Value representing the sum of all (successful and unsuccessful) page loads for a selected time period. Used to calculate the success and error rate.
synthetics.error_rate Percent (%)

Error Rate. Percentage of the tests that ran during the specified time period and failed. A test fails if an error prevents the website(s) from loading.

Found in: Metrics Explorer, Entity Explorer, DEM area overview

synthetics.errors Count Value representing the sum of unsuccessful page loads for a selected time period. Used to calculate the error rate.
synthetics.overall_status.duration Seconds (s) Value representing the amount of time the website had its last status (up or down).
synthetics.overall_status.duration.total Seconds (s) Value representing the total time the entity had a given status (up, down, paused, unknown, or in maintenance) for a specified time period.
synthetics.ping.packet_loss Count Value representing the number of failed ping responses.
synthetics.ping.response.time milliseconds (ms) Time required to send data from a user's device to the server.
synthetics.http.response.time milliseconds (ms)

HTTP Response Time, Average HTTP Response Time History. Time required to perform an HTTP GET command to retrieve the webpage(s) during the specified time period.

HTTP communications between SolarWinds Observability SaaS and configured entities are not encrypted.

May be displayed as:

  • Average HTTP Response Time. Average time required to perform an HTTP GET command to retrieve the webpage(s) during the specified time period.

  • Average Response Time History. The average HTTP response times during the specified time period. Use this chart, for example, to identify time periods when response time is typically higher than usual.

Found in: Metrics Explorer, Entity Explorer, Inspector Panel.

synthetics.https.certificates.days_to_certificate_expiration Days The number of days between today and the date the website's SSL/TLS certificate expires.
synthetics.https.response.time milliseconds (ms) HTTPS Response Time, Average HTTPS Response Time History. Time required to perform an HTTPS GET command to retrieve the webpage(s).

HTTPS communications are encrypted using Transport Layer Security (TLS).

May be displayed as:

  • Average HTTPS Response Time. Average time required to perform an HTTPS GET command to retrieve the webpage(s) during the specified time period.

  • Average Response Time History. The average HTTPS response times during the specified time period. Use this chart, for example, to identify time periods when response time is typically higher than usual.

Found in: Metrics Explorer, Entity Explorer, Inspector Panel.

synthetics.response.time.avg   Value representing the average response time across all monitored entities for the specified time period.
synthetics.status Boolean Status of a test result, where 0 indicates the website is unavailable and 1 indicates the website is available.
synthetics.success_rate Percent (%)

Success Rate. Percentage of the tests that ran during the specified time period and were successful. A test is successful if SolarWinds Observability SaaS is able to load the website(s). and it fails if an error prevents the website(s) from loading. An average of this metric is used to include availability in the health score.

Found in: Metrics Explorer, Entity Explorer, DEM area overview

synthetics.successes Count Value representing the sum of successful page loads for a selected time period. Used to calculate the success rate.
synthetics.tcp.response.time milliseconds (ms) Time required to see if a port is open on a specified address.

Synthetic transaction metrics

Metric Units Description
composite.synthetics.availability Percent (%) Status Changes, Status History. Represents if a synthetic transaction is available or unavailable.

 

Found in: Metrics Explorer, Entity Explorer (Overview tab)

composite.synthetics.status.downtime.count Count

Value representing the number of times the synthetic transaction entity was down in a given time range.

For example, if the entity was down the entirety of the time range, the count would be 1.

composite.synthetics.status.downtime.total Seconds (s) The total downtime for the entity during the specified time range.
synthetics.overall_status.duration.total Seconds (s) The total amount of time the entity had a given a status.
synthetics.overall_status.duration Seconds (s) The amount of time in seconds the entity had a given status.
synthetics.transaction.attempts Count The number of attempted executions of your synthetic transaction for the selected time period.
synthetics.transaction.duration Seconds (s)

Historical Overview. The amount of time in seconds that it took your synthetic transaction to complete its execution.

May be displayed as:

  • Average Test Duration. Average time it took for your synthetic transaction to complete its execution.

synthetics.transaction.error_rate Percentage (%) Test Success Rate. Value representing the percentage of failed transaction attempts for the selected time period.
synthetics.transaction.errors Count Test Success Rate. Value representing the sum of failed transaction attempts for the selected time period. Used to calculate the Synthetic transaction error rate.
synthetics.transaction.result Count The number of times the synthetic transaction resulted in a success or error.
synthetics.transaction.success_rate Percentage (%) Test Success Rate. Value representing the percentage of successful transaction attempts for the selected time period.
synthetics.transaction.successes Count Test Success Rate. Value representing the sum of successful transaction attempts for the selected time period. Used to calculate the Synthetic transaction success rate.

Real user monitoring (RUM) metrics

The following table lists some of the critical metrics collected for these entities. To see the website's RUM metrics in the Metrics Explorer, type rum. in the search box.

Metric Units Description
composite.rum.session.bounce_rate Percent (%) Bounce Rate. The percentage of users who abandon the website immediately after landing on one of its pages.
rum.pageview.apdex_score  

Apdex score. A measurement of user satisfaction, using the Application Performance Index standard to specify the degree to which measured performance meets user expectations. The satisfactory load time, tolerating, and frustrated load times are defined when creating the website entity. For more information about the Apdex standard, Defining the Application Performance Index.

If the response time for requests takes less time than the satisfied load time threshold set for your website, the Apdex score is considered a satisfied load time. It is a tolerating load time if the response time takes up to four times the satisfied load time threshold, and a frustrated load time if it takes longer than four times the satisfied load time threshold.

rum.pageview.client_processing seconds (s) Client Processing Time. Measurement of the time from when the browser sends the initial HTTP request until all synchronous load events have been processed, including layout and running scripts.
rum.pageview.count Count PageViews. Count of the views of your webpage(s).
rum.pageview.load_time seconds (s) Load Time. The amount of time for the website to fully load.
rum.pageview.ttfb seconds (s) Time to First Byte. The amount of time between when the browser requested a page and when it received the first byte of information from the server.
rum.web_vitals.largest_contentful_paint seconds (s)

Largest Contentful Paint. A measurement of how quickly the largest image or text content of a web page is loaded.

Largest contentful paint time is considered good if loading the largest image or text block takes less than 2.5 seconds, needs improvement if it takes up to 4.0 seconds, and poor if it takes longer than 4.0 seconds.

rum.web_vitals.interaction_to_next_paint milliseconds(ms)

Interaction to Next Paint. A measurement of how quickly the website responds to user interactions such as clicks and key presses.

Interaction to next paint time is considered good if the response to a customer's first interaction with the website is below or at 200ms, needs improvement if it takes up to 500ms, and poor if it takes longer than 500ms.

rum.web_vitals.cumulative_layout_shift  

Cumulative Layout Shift. Measures how much a webpage shifts unexpectedly while a user is viewing the webpage. A shift may occur if content loads at different speeds or if elements are added to the website dynamically.

A cumulative layout shift value of less than .1 is considered good, a value up to .25 needs improvement, and a value greater than .25 is poor.

rum.web_vitals.first_input_delay seconds (s)

First Input Delay. Time from when a user first interacts with your site to the time when the browser is able to respond to the interaction. First input delay (FID) helps measure the first impression a user has of your site's responsiveness.

The FID is considered good if responding to a customer’s first interaction with the site takes less than 100ms, needs improvement if it takes up to 300 ms, and poor if it takes longer than 300 ms.

rum.session.count   Sessions, Top 10 countries by session. The total number of sessions, or visits, to the website during the selected time period and by country. A single session includes every action that the user takes during the entirety of their visit to the website.