Core Assurance Observations

Core Assurance is currently in beta. Features may change, documentation may be out of date, and performance may be inconsistent. Use at your own discretion.

An observationClosed 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. is the main signal that something is wrong at scale. A single failed test on one endpoint does not raise an observation. Core Assurance raises an observation only when the percentage of online test endpointsClosed 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. that fail a test profileClosed A reusable Core Assurance definition of a synthetic test. A test profile sets what to test, what counts as a passing run, when the test runs, which test endpoints run it, and what to do when enough endpoints fail. is above the trigger set in the action policyClosed The part of a Core Assurance test profile that decides when to act and what to do. An action policy sets the failure trigger, the dampening period, and whether to create an observation, run an automation, or both. of the profile. Offline endpoints are not counted in the failure percentage. Requiring a percentage of endpoints to fail keeps your team focused on problems that affect many users, not on noise from a single endpoint.

You set the trigger, the dampening periodClosed A Core Assurance cool-down period that starts when the failure percentage for a test profile is no longer above its trigger. New failed runs are still logged during the dampening period, but no new action is taken. The related observation closes when the period ends., and whether to create an observation on the Action Policy tab of a test profile. See Action Policy tab. For how offline endpoints and other limits affect the calculation, see Core Assurance Operational Notes and Limits.

How a test profile raises and closes an observation

Two things change as a problem starts and ends. The test profile moves between alert statuses, which you see on the Test Profiles page. The observation is either open or closed, which you see on the Observations page. The profile status decides when the observation opens and closes.

Each test profile moves through the following transitions:

  • Active: The profile is enabled and the failure percentage is not above the trigger. No observation is open for the profile.

  • Active to Alerting: The percentage of online endpoints with a failed test is above the trigger. Core Assurance opens an observation and takes the other actions set in the action policy.

  • Alerting to Dampening: The failure percentage is no longer above the trigger. The dampening period starts. The observation stays open.

  • Dampening to Alerting: The failure percentage rises above the trigger again before the dampening period ends. The profile returns to Alerting, and the same observation stays open.

  • Dampening to Active: The dampening period ends without the trigger being met again. The observation closes.

Use the following table to decide how to respond to each status:

Profile status

Observation

What it means for you

Alerting

Open

The trigger condition is met. Treat the observation as an active issue.

Dampening

Open

The condition cleared recently. Wait for the dampening period to end before you treat the issue as resolved.

Active

Closed

The dampening period ended without the trigger being met again. The issue has ended.

A profile that is turned off shows Inactive and does not raise observations. For all profile statuses, see Profile statuses.

Work with Core Assurance observations