Documentation forSolarWinds Observability SaaS

Website and URI 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.

General website and URI metrics

The following table lists the general metrics collected for these entities.

Metric Units Description
sw.metrics.healthscore %

Health score. A health score provides real-time insight into the overall health and performance of your monitored entities. The health score is calculated based on anomalies detected for the entity, alerts triggered for the entity's metrics, and the status of the entity. The health score is displayed as a single numerical value that ranges from a Good (70-100) to Moderate (40-69) to Bad (0-39) distinction.

To view the health score for website entities in the Metrics Explorer, filter the sw.metrics.healthscore metric by entity_types and select website.

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
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)
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.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.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.

Synthetic transaction metrics

Metric Units Description
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.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
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.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.