Test Profiles
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. is a reusable definition of one synthetic test
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.. Each test profile tells Core Assurance what to test, how to judge each run, when to run the test, which 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. run the test, and what to do when enough endpoints fail. You build and manage test profiles on the Test Profiles page.
Parts of a test profile
A test profile has six parts. Each part has its own tab when you create or edit the test profile.
-
Basic info: The name of the test profile, whether the profile is active, the test type, and an optional related application
An entity type representing software applications deployed in the customer environment that are monitored for performance and anomalies.. The test type decides which kind of check the endpoints run, such as a ping or a web request. See Core Assurance Supported Test Types. -
Definition: The target of the test, such as a host name or web address, and the settings for the check, such as the timeout.
-
Pass criteria: The conditions a single run must meet to pass, such as a maximum response time or an expected status code. A run that does not meet the pass criteria fails. Each 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.. -
Frequency: When the test runs. Tests run every 15 minutes during the daily active hours and the days of the week you choose.
-
Deployment: The test endpoints that run the test. You can also deploy a test profile to more endpoints later from the Test Endpoints page.
-
Action policy: 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. decides when Core Assurance acts and what it does. The action policy sets the trigger, which is the percentage of online endpoints that must fail before Core Assurance acts, and 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.. The action policy also sets whether Core Assurance creates 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., runs 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., or both. Offline endpoints are not counted in the failure percentage.
For every field on every tab, see Test profile tabs.
Profile statuses
Each test profile has a status that shows whether the profile is running and whether the profile has an open observation.
|
Status |
Meaning |
|---|---|
|
Active |
The profile is turned on and runs on its assigned endpoints. No observation is open. |
|
Inactive |
The profile is turned off and does not start new test runs. The settings and history of the profile are kept. |
|
Alerting |
The trigger condition is met, and an observation for the profile is open. |
|
Dampening |
The failure percentage is no longer above the trigger, and the profile is in its dampening period. The observation stays open until the dampening period ends. |
Sync status is tracked separately from profile status. A profile of any status can also be Pending Sync
A sync status that means a test profile deployment is saved in the cloud, but one or more assigned endpoints have not yet applied and confirmed it. while its assigned endpoints confirm a new configuration. See Sync statuses. For how a profile opens and closes an observation, see Core Assurance Observations.
Work with test profiles
-
Test Profiles Page: The list of test profiles and every tab you use to create and edit a profile.
-
Create a Test Profile: Set up a new test profile and send the profile to endpoints.
-
Edit, Disable, or Delete a Test Profile: Change, pause, or remove an existing test profile.