WEBVTT

00:00:00.250 --> 00:00:05.993
Open Administration, General, Alert Routing in the fictional Summit Managed IT staging

00:00:05.993 --> 00:00:11.537
workspace. This page chooses notification destinations for matching alerts. We will

00:00:11.537 --> 00:00:17.146
prepare a Northwind Traders route without saving it. No email or webhook delivery is

00:00:17.146 --> 00:00:19.150
attempted in this walkthrough.

00:00:20.370 --> 00:00:25.715
The highlighted sentence states the default. Routes never replace it: every owner and

00:00:25.715 --> 00:00:31.311
administrator still gets each alert that Alert Rules set to notify, or the storm incident

00:00:31.311 --> 00:00:36.971
that groups it. Routes add recipients and webhooks for anyone else who needs to hear about

00:00:36.971 --> 00:00:42.567
an alert. Plan coverage for every customer and alert category before activating a routing

00:00:42.567 --> 00:00:42.945
setup.

00:00:44.121 --> 00:00:49.770
Use a name that describes the customer and purpose. Select Northwind Traders as the

00:00:49.770 --> 00:00:55.282
customer. Leave Any check selected for this draft so we can focus on customer and

00:00:55.282 --> 00:01:01.271
severity. In a real setup, review the check filter together with your intended coverage.

00:01:02.439 --> 00:01:08.356
Minimum severity offers warning plus critical, or critical only. Select critical only for

00:01:08.356 --> 00:01:14.340
this example. Notify on resolve requests a follow-up when a matching alert resolves. Check

00:01:14.340 --> 00:01:20.190
this choice with your on-call process so the team can distinguish a new problem from its

00:01:20.190 --> 00:01:20.789
recovery.

00:01:21.961 --> 00:01:27.900
The Emails field accepts comma-separated destinations. We enter a reserved example address

00:01:27.900 --> 00:01:33.839
for this draft. The webhook field is optional; keep real webhook URLs private because they

00:01:33.839 --> 00:01:38.986
can act as credentials. We leave it blank and do not send a test notification.

00:01:40.159 --> 00:01:45.955
Review the customer, check filter, severity, resolution setting and destinations together.

00:01:45.955 --> 00:01:51.687
Add route would save the route and change notification behavior. We do not press it here.

00:01:51.687 --> 00:01:57.097
Cedar Valley Dental and Harborline Logistics need their own planned coverage if they

00:01:57.097 --> 00:01:59.609
should receive different notifications.

00:02:00.813 --> 00:02:06.438
Recent webhook attempts provides evidence about attempted webhook requests. Read the

00:02:06.438 --> 00:02:12.398
recorded status and time. Provider accepted describes the provider response, and does not

00:02:12.398 --> 00:02:18.024
by itself prove that a person saw the message. An empty history does not demonstrate

00:02:18.024 --> 00:02:19.363
successful delivery.

00:02:20.554 --> 00:02:26.561
Reopen Alert Routing to discard the unsaved example. For an authorized rollout, save the

00:02:26.561 --> 00:02:32.705
reviewed route, reopen it to verify the stored configuration, and exercise both a matching

00:02:32.705 --> 00:02:38.712
and a nonmatching alert in a test environment. Confirm the intended destination receives

00:02:38.712 --> 00:02:43.354
the matching notification and verify resolution behavior separately.
