WEBVTT

00:00:00.250 --> 00:00:06.213
This walkthrough shows Alert Rules in Administration, General. We are using the fictional

00:00:06.213 --> 00:00:12.177
Summit Managed IT staging workspace. Alert Rules decides which events qualify for alerts;

00:00:12.177 --> 00:00:18.140
Alert Routing decides who receives notifications. We will prepare examples without saving

00:00:18.140 --> 00:00:20.150
or changing active monitoring.

00:00:21.348 --> 00:00:27.680
The Alert engines matrix separates opening an alert from its severity, case, notification

00:00:27.680 --> 00:00:33.799
and ticket settings. Device thresholds are managed in agent policies. Select Syslog to

00:00:33.799 --> 00:00:40.132
inspect that engine. Save alert rules applies matrix changes, so review the entire set of

00:00:40.132 --> 00:00:41.698
changes before saving.

00:00:43.751 --> 00:00:49.623
Scroll to New syslog rule. Give the rule a descriptive name and select Northwind Traders

00:00:49.623 --> 00:00:55.495
as the customer. A customer-specific rule prevents the same example from matching events

00:00:55.495 --> 00:01:01.167
from Cedar Valley Dental or Harborline Logistics. Leave the example unsaved while you

00:01:01.167 --> 00:01:02.301
review its scope.

00:01:04.542 --> 00:01:10.616
Match severity at or below uses syslog numbers: lower numbers are more urgent. Three

00:01:10.616 --> 00:01:17.125
includes error, critical, alert and emergency events. Raise alert as selects the resulting

00:01:17.125 --> 00:01:23.417
RMM alert severity. Here we use error or more urgent events and raise them as critical.

00:01:24.616 --> 00:01:30.660
Use host, app and message filters to narrow the match. This example looks for a Northwind

00:01:30.660 --> 00:01:36.773
firewall host, the sshd app tag and an authentication failure message. These are fictional

00:01:36.773 --> 00:01:42.750
values. Inspect real authorized sample events before choosing a production match; a full

00:01:42.750 --> 00:01:44.991
log line may vary between events.

00:01:47.599 --> 00:01:53.175
Enabled controls whether the saved rule is active. Also open a ticket is a separate

00:01:53.175 --> 00:01:59.155
choice. We turn Enabled off in this unsaved example and leave ticket creation off. Review

00:01:59.155 --> 00:02:04.865
the scope and match before using Add rule. This recording does not submit the form or

00:02:04.865 --> 00:02:06.074
generate an alert.

00:02:07.285 --> 00:02:13.746
New SNMP rule uses the same customer scoping. Here we prepare a Cedar Valley Dental switch

00:02:13.746 --> 00:02:20.065
CPU rule, narrow the metric to CPU, and choose a numeric threshold. A match filter alone

00:02:20.065 --> 00:02:26.526
is not a threshold: the operator and number must be supplied together, or a status keyword

00:02:26.526 --> 00:02:27.460
must be used.

00:02:28.657 --> 00:02:34.263
We leave both forms unsaved and reopen Alert Rules to discard them. For an authorized

00:02:34.263 --> 00:02:39.803
rollout, save the reviewed rule, reopen it to check the stored values, then verify a

00:02:39.803 --> 00:02:45.606
matching event and a nonmatching event. Check any resulting alert and ticket separately.

00:02:45.606 --> 00:02:50.882
Saving configuration alone does not establish that collection or delivery works.
