Core Assurance Landing Page
The Core Assurance landing page is your operational home page for synthetic testing
A scheduled test that an endpoint starts on its own to check whether a target is reachable and performing well. A synthetic test measures the response to traffic the test itself creates, not passive user traffic.. It summarizes your test profiles, 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., and test runs over the last 24 hours, and it gives you one-click access to the other Core Assurance pages. Start here when you want a quick read on whether your monitored services are healthy.
Navigate to the Core Assurance landing page:
-
Click Apps in the left menu.
-
Click Apps Library.
-
Click the Core Assurance card.
Summary cards
The top of the page shows four summary cards. Each card has a button that opens the related page.
|
Card |
What it shows |
Button and destination |
|---|---|---|
|
Test Profiles |
The number of test profiles in your tenant. |
Show Test Profiles opens the Test Profiles page. |
|
Test Endpoints |
The number of test endpoints in your tenant. |
Show Test Endpoints opens the Test Endpoints page. |
|
Tests in Last 24h |
The number of test runs in the last 24 hours. |
Show Tests opens the Test Results page. |
|
Failed Tests in Last 24h |
The number of test runs with a status of Fail in the last 24 hours. |
Show Failed Tests opens the Test Results page filtered to show only failed tests. |
A card shows a dash in place of its number when its data cannot be loaded. The Show Test Profiles and Show Test Endpoints buttons appear only when your account can open the Test Profiles and Test Endpoints pages.
Test Runs chart
The Test Runs chart plots test activity over the last 24 hours. The chart shows two measures:
-
Total test runs: How many tests ran in each time interval.
-
% Test Failure: The percentage of test runs in each time interval that failed.
Use the chart to spot spikes in failures and to line them up with change windows or other events. To investigate a spike, note its time, then open the Test Results page and set the time range to match. See Investigate a Spike in Test Failures.
Triage tips
-
Check the Failed Tests in Last 24h card first when you triage. A rising count is the fastest sign that something has changed.
-
Review open observations
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. on the Observations page. An observation stays open while its test profile is alerting, and while the profile waits out its dampening period after the failure percentage is no longer above the trigger. The observation closes when the dampening period ends. See Core Assurance Observations. -
To see which test profiles are alerting or dampening, open the Test Profiles page and check the Alerting and Dampening cards.
Beta legal agreement
The Beta legal agreement link at the bottom of the page opens the Core Assurance Beta page. The Core Assurance Beta page shows who accepted the Core Assurance terms for your tenant and when. The link appears when your account can read feature opt-in settings.