Core Assurance Operational Notes and Limits
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 observation |
|
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 endpoints |
|
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 |
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 Protocol |
For details on each setting, see Test profile tabs.