Concorbit HelpAll guides →

Monitoring

Component monitors

Component monitors go beyond basic metrics to check specific services, processes, certificates, and custom conditions on your devices. Each monitor runs on a schedule and reports healthy, warning, or critical state.

Monitor catalogue

concorbit RMM includes a catalogue of pre-built monitor types:

Performance

  • CPU usage, memory usage, disk space, network throughput, temperature

Services

  • Windows service state (check that a named service is running)

  • Process count (alert if a process is not running or has too many instances)

Security

  • Windows Defender status (enabled, definitions up to date)

  • Firewall state

  • Failed logon attempts (threshold over time)

System events

  • Disk errors, blue screens (BSOD), unexpected shutdowns

  • Pending reboot detection

Advanced

  • Event log monitoring (match specific event IDs or sources)

  • File existence and modification checks

  • HTTP health check (URL returns expected status code)

  • Ping check (host responds within timeout)

  • DNS resolution check

  • TLS certificate expiry (alert X days before expiry)

  • Backup job status (check Windows backup or custom backup tools)

Monitoring policies

Policies define which monitors are active and at what scope.

Scope chain

Monitors can be configured at four levels. The most specific wins:

  1. Organisation: default for all devices

  2. Device type: override for workstations, servers, laptops, or Macs

  3. Site: override for a specific site

  4. Device: override for an individual device

Device type is detected automatically based on the operating system and hardware (desktop vs laptop vs server).

Configuring a policy

Go to Settings > Monitoring policies to view and edit the scope chain. Each monitor can be:

  • Enabled with custom thresholds

  • Disabled to suppress at this scope

Example: enable the "Disk space" monitor at the organisation level with a 90% threshold, but override it to 95% for a specific server.

Monitor state

View monitor state on any device's Monitoring tab. Each monitor shows:

  • Current state: healthy (green), warning (amber), or critical (red)

  • Last message (what the monitor found)

  • Last run time and schedule

  • A mini sparkline of recent state changes

Alerts from monitors

When a monitor transitions to warning or critical, it raises an alert. The alert follows your alert policy for severity, notification channels, and cooldown. When the monitor returns to healthy, the alert resolves automatically.