Observation Updates and Automation
The action policy
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 a test profile
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. controls what Core Assurance does when the trigger is met, and how Core Assurance handles failures that continue after the trigger is met. You set the action policy on the Action Policy tab. See Action Policy tab.
-
If Create Observation is turned on, Core Assurance opens one 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. for the test profile when the trigger is first met. -
While the profile is Alerting, new failing 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. update the same observation. Core Assurance does not open a separate observation for each additional failing endpoint. -
If Run Automation is turned on, Core Assurance runs the selected on-demand runbook
A runbook that triggers as required, either manually on-demand or as scheduled, to collect critical data and assist users with investigation tasks. as an automation
Automated procedures that are executed as the result of a trigger. Automations consist of a single entry point and a sequence of connected nodes that define the processing logic. when the trigger is met. See On-Demand Runbooks. -
During the dampening period
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., new failed runs are still logged, but Core Assurance takes no action on the new failed runs.
For how a test profile moves between statuses as the observation opens and closes, see Core Assurance Observations.