Configure alert-rule matching for a customer Fictional staging demonstration. The forms are prepared but not saved. No alert generation, ticket creation or notification delivery is demonstrated. This walkthrough shows Alert Rules in Administration, General. We are using the fictional Summit Managed IT staging workspace. Alert Rules decides which events qualify for alerts; Alert Routing decides who receives notifications. We will prepare examples without saving or changing active monitoring. The Alert engines matrix separates opening an alert from its severity, case, notification and ticket settings. Device thresholds are managed in agent policies. Select Syslog to inspect that engine. Save alert rules applies matrix changes, so review the entire set of changes before saving. Scroll to New syslog rule. Give the rule a descriptive name and select Northwind Traders as the customer. A customer-specific rule prevents the same example from matching events from Cedar Valley Dental or Harborline Logistics. Leave the example unsaved while you review its scope. Match severity at or below uses syslog numbers: lower numbers are more urgent. Three includes error, critical, alert and emergency events. Raise alert as selects the resulting RMM alert severity. Here we use error or more urgent events and raise them as critical. Use host, app and message filters to narrow the match. This example looks for a Northwind firewall host, the sshd app tag and an authentication failure message. These are fictional values. Inspect real authorized sample events before choosing a production match; a full log line may vary between events. Enabled controls whether the saved rule is active. Also open a ticket is a separate choice. We turn Enabled off in this unsaved example and leave ticket creation off. Review the scope and match before using Add rule. This recording does not submit the form or generate an alert. New SNMP rule uses the same customer scoping. Here we prepare a Cedar Valley Dental switch CPU rule, narrow the metric to CPU, and choose a numeric threshold. A match filter alone is not a threshold: the operator and number must be supplied together, or a status keyword must be used. We leave both forms unsaved and reopen Alert Rules to discard them. For an authorized rollout, save the reviewed rule, reopen it to check the stored values, then verify a matching event and a nonmatching event. Check any resulting alert and ticket separately. Saving configuration alone does not establish that collection or delivery works.