Core Assurance Overview

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.

Core Assurance helps you find application and network path problems before your users report them. It runs synthetic testsClosed 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. from 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. in your environment, which are user devices that have the Core Assurance module installed. The endpoints send their results to the Riverbed Technology cloud. When enough endpoints fail the same test, Core Assurance raises 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. so your team can act.

Read the following sections to learn what Core Assurance does, how its parts fit together, and where to find each part in the documentation. To start using Core Assurance, see Getting Started with Core Assurance.

What Core Assurance helps you answer

Use Core Assurance when you need to know:

How Core Assurance works

Everything in Core Assurance starts with 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.. A test profile defines one synthetic test: the type of check, the target, what counts as a passing run, the schedule, the test endpoints that run the test, and 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. that decides what happens when enough endpoints fail.

Each test endpoint runs its assigned test profiles on schedule and sends every result to the cloud. When the percentage of online endpoints that fail a test profile is above the trigger in the action policy, Core Assurance opens an observation and can run an automationClosed 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 failure percentage is no longer above the trigger, the test profile enters a 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.. The observation closes when the dampening period ends.

For a diagram of the full cycle, see Core Assurance Workflow.

Parts of Core Assurance

Each part of Core Assurance has its own section in the documentation. Each section starts with a concept topic and continues with page descriptions and procedures.

  • Landing page: Summary counts for test profiles, test endpoints, tests, and failed tests, plus a chart of test runs over time. See Core Assurance Landing Page.

  • Test profiles: What a test profile contains, its statuses, and how to create and manage profiles. See Test Profiles.

  • Test types: The six kinds of check a test profile can run, and the settings for each kind. See Core Assurance Supported Test Types.

  • Test endpoints: How endpoints receive test profiles, how sync works, and how to deploy profiles to endpoints. See Test Endpoints.

  • Test results: How Core Assurance records each run, and how to investigate runs across endpoints or on one endpoint. See Test Results and Test Details.

  • Observations: How a test profile opens and closes an observation, and how to work an observation. See Core Assurance Observations.

How Core Assurance works with the rest of the platform

Core Assurance shares data and actions with other parts of Riverbed IQ: