Service Check Reference

All parameters, thresholds, and configuration options for the Service Check in octoja.

Written By Erdinc Akay

Last updated About 1 month ago

This article describes the available configuration options and the behaviour of the Service Check. In the check list it appears as Service Status (DE: Dienststatus).

Configuration Fields

Field	Type	Required	Default	Description
Services to monitor	array of strings	Yes when Monitor auto-start services is off — leaving it empty produces a Warning result	—	Service names to check, as shown in the OS. Supports wildcards: `` (any characters) and `?` (single character), e.g. `SQL`
Monitor auto-start services	boolean	No	off	When enabled, the check automatically monitors every service configured to start automatically, instead of using an explicit list
Excluded services	array of strings	No	—	Service names to exclude from monitoring. Only used when Monitor auto-start services is on. Supports wildcards: `` (any characters) and `?` (single character), e.g. `Xbox`

When the device has reported its installed services, the Services to monitor and Excluded services dropdowns list each service by its friendly display name with the underlying service name in parentheses — for example Windows Update (wuauserv). Selecting an entry stores the underlying service name, and the chip shown in the field always displays that exact name, so the stored value stays unambiguous regardless of the display name.

Service statuses

Status	Meaning
Running	Service is active — check passes
Stopped	Service is not running — critical result
Not Found	Service is not installed on the device — critical result
Unknown	The agent could not query the service's state — the check reports an Error result

On Linux, the status column shows the systemd state reported by systemctl is-active — for example Active, Inactive, Failed, Activating, or Deactivating. Any state other than Active counts as a critical result.

Result behaviour

The Service Check is read-only — it reports each service's running state without changing it. When every monitored service is running, the check returns a success result. As soon as one monitored service is stopped or not found, the check returns a critical result and lists the affected services in the result detail. If a service's state cannot be queried, the check reports an Error result. If no services match the configuration at all — an empty explicit list, or an auto-start selection where every service is excluded — the check returns a Warning result.

See also: Configure a Service Check