Monitor an Application with Core Assurance

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.

Create 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. when you want Core Assurance to check a service on a schedule and alert your team when enough 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. fail. The example values in the following procedure suit a business application used during working hours. For the full procedure and every setting, see Create a Test Profile.

Navigate to the Test Profiles page:

  1. Click Apps in the left menu.

  2. Click Apps Library.

  3. Click the Core Assurance card.

  4. On the Test Profiles card, click Show Test Profiles.

To monitor an application with Core Assurance:

  1. Click Create Test Profile.

  2. On the Basic Info tab, enter a name and choose a test type, such as HTTP URL for a web application or Ping for basic reachability. Optionally, choose the related applicationClosed An entity type representing software applications deployed in the customer environment that are monitored for performance and anomalies..

    1. HTTP stands for Hypertext Transfer ProtocolClosed Hypertext Transfer Protocol. A protocol used for transmitting data over the internet, commonly used in webhook runbooks and integrations with external systems., and URL stands for Uniform Resource LocatorClosed Uniform Resource Locator. The address used to access resources on the internet, such as webhook endpoints or API endpoints for runbook automation.. For help choosing a type, see Core Assurance Supported Test Types.

  3. On the Definition tab, enter the target and the timeout.

  4. On the Pass Criteria tab, set what counts as a successful run.

  5. On the Frequency tab, set the active hours and days. For example, run the test from 08:00 to 18:00, Monday through Friday.

  6. On the Deployment tab, select the endpoints at the sites you want to monitor.

  7. On the Action Policy tab, set the trigger, the dampening period, and the actions. For example, set the trigger to 25% of online endpoints with a failed test, set a 30-minute dampening period, and leave Create Observation on.

  8. Click Save.