Test Results and Test Details
Core Assurance records every test run that your test endpoints
A user device, such as a laptop or desktop computer, that has the Core Assurance module installed and runs synthetic tests. Each test endpoint receives test profiles from the cloud, runs them on schedule, and sends its results back. complete. Each run has a status of Pass or Fail, a response time, and, for a failed run, an error that explains why the run failed. A failed run is a violation
A single test run that fails, either because the result does not meet the pass criteria or because the test times out. In Core Assurance, a violation is recorded as a test status of Fail..
Two views of the same runs
Core Assurance shows test runs on two pages. Each page answers a different question.
-
Test Results: Which test profiles, applications, or endpoints are failing across your whole fleet? The Test Results page lists runs from all endpoints and all profiles, with search and filters. See Test Results Page.
-
Test Details: How has one test profile performed on one endpoint over time? The Test Details page shows a response time chart and the run history for a single profile on a single endpoint. See Test Details Page.
During an investigation, start on the Test Results page to find where failures are concentrated. Then open the Test Details page for a failing run to see whether the endpoint has been degrading gradually or failing suddenly. See Determine Whether Failures Are Isolated or Widespread.
How long results are kept
Results from online endpoints usually appear within about two minutes after a run completes. Raw results are kept for 30 days. The Test Results page shows up to 14 days at a time, and you can move the time range anywhere within the 30-day retention window. See Core Assurance Operational Notes and Limits.
When enough endpoints fail the same test profile, Core Assurance raises an observation
A record of a condition in your environment that needs attention. Observations appear on the Observations page and in the Observation Feed widget, and they move through lifecycle states. For example, Core Assurance creates an observation when the percentage of online endpoints that fail a test is at or above the trigger set in the test profile.. See Core Assurance Observations.