Core Assurance Operational Notes and Limits

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.

The following behaviors and limits affect how you read the data in Core Assurance. Review them before you rely on results for reporting or for decisions during an incident.

Data timing and retention

Area

Behavior

Results visibility

Results from online endpoints usually appear within about two minutes after a run completes.

Observation evaluation

Core Assurance checks results against the trigger after it receives them. 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. usually opens or updates within about five minutes after the endpoint sends its results.

Raw results retention

Raw results are kept for 30 days for investigation.

Test Results time range

The Test Results page shows up to 14 days at a time. To review older runs, move the range to any period within the 30-day retention window.

Endpoint behavior

Area

Behavior

Offline endpoints

Offline 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. are not counted when Core Assurance calculates the failure percentage for an observation. Scheduled runs that an endpoint misses while it is turned off or asleep are not run later.

Lost cloud connection

If an endpoint cannot reach the cloud, it keeps running its scheduled tests and stores recent results locally. It uploads them when the connection returns. The endpoint stores the last 100 results for each test profile.

Per-endpoint capacity

Limits apply to how many tests you can assign to an endpoint and how many tests can run on it at the same time. The limits are set for your tenant and are not shown in the product. A run that exceeds the concurrent limit fails with the CONCURRENT_LIMIT_EXCEEDED code. If you see the CONCURRENT_LIMIT_EXCEEDED code often, assign fewer profiles to the endpoint, or contact Riverbed Technology Support. See Failure codes for more than one test type.

Test profile limits

Setting

Limit

Run frequency

Tests run every 15 minutes during the active hours and days you set. Tests run on a repeating schedule only.

Trigger

A whole number from one to 100 percent of online endpoints. The default is 25.

Dampening period

A whole number from one to 1440 minutes (24 hours). The default is 30.

HTTP method

HTTP (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.) URL (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.) tests use the GET method.

For details on each setting, see Test profile tabs.