Validate a Change Window

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.

Use a Core Assurance test profile to confirm that a planned change, such as a network or application update, does not break service for your users.

Note: Tests run every 15 minutes during active hours. Results take about two minutes to appear, and Core Assurance takes about five minutes to evaluate the results against the trigger. After the change, allow one full 15-minute interval plus about seven more minutes, roughly 25 minutes in total, before you confirm the result.

To validate a change window:

  1. Create a test profile, or reuse an existing test profile, that checks the service affected by the change. See Create a Test Profile.

  2. On the Frequency tab of the test profile, make sure the active hours and days cover the change window.

  3. Deploy the test profile to the endpoints at the affected sites. See Deploy or Undeploy a Test Profile.

  4. During and after the change, watch the runs for the test profile on the Test Results page. See Test Results Page.

  5. Confirm that no observation opens, or that any observation that opened closes at the end of its dampening period.

  6. If you no longer need the test profile, disable or delete the test profile. See Edit, Disable, or Delete a Test Profile.