Service Monitoring

Entry: /monitoring. Monitoring owns service probes, device observations, alert rules, maintenance and incidents. You need the appropriate Group and monitor or collection-management permission. Confirm that the installation can reach the approved target and that required workers, adapters and credentials are configured; saving a target alone does not prove collection is operating.

Create a service monitor

1. Open Monitors and choose Create Monitor. Enter a name and select the supported probe kind, such as HTTPS, TCP, DNS or TLS.
2. Enter the target and set the interval, timeout and applicable expected status or content assertion. Service-monitor intervals range from 60 seconds to 86,400 seconds; the timeout must satisfy the form's validation.
3. Submit, open the monitor detail and inspect Recent checks, status and observation time after the worker has run.
4. Use Availability or the monitor's Availability report to review the chosen reporting window. Missing or failed collection is not a successful check.

Configure alerting and handle an incident

1. In the monitor's permitted operations, configure its alert rule: failures before an incident, successes before automatic resolution, severity and any escalation policy.
2. Schedule Maintenance for planned work with the correct start, end and reason. Confirm the saved window before relying on its alerting effect.
3. Inspect Incident history when an incident occurs. Use Acknowledge Incident when you take responsibility, and Resolve Incident with a meaningful note after verification.
4. Check the actual configured notification destination. Selecting an email or webhook channel does not itself configure an external delivery provider.

Configure device performance collection

1. Open Collection Settings → Add collection target. Choose the standalone or eligible inventory source, target details, Device profile and required collection settings.
2. Save the target, then use its Settings to select the supported CPU, memory, interface, power-supply and fan components. Review available named interfaces rather than assuming every component is supported.
3. Choose Save collection settings, request Check now when available, and inspect Network Performance and its component history. Use Device Logs and Traffic Analysis for configured receiver evidence.

Limits and boundaries: device customization supports 512 selected components and 32 custom definitions per target, with a 256 KiB customization bound; manual collection has a 60-second cooldown. Vendor/firmware coverage varies. Custom MIB definitions require verified device knowledge; ICMP requires its separate configured adapter. Managed/Unmanaged inventory state can stop linked collection. Monitoring observes targets; it does not provision them, change their inventory or guarantee physical-device compatibility from a generic profile.