PANTAW COLLECTOR · SYSTEM

systemd collector

Observe configured Linux unit state without controlling the unit.

Source and collected facts

A fixed read-only systemctl show query through the shared command helper.

load, active and sub-state
unit-file state and description
main PID, result and exit status
fragment path when exposed

Observation contract

Active units can be SUCCESS; inactive, failed, incomplete or inaccessible units map deterministically to FAILURE, PARTIAL or UNAVAILABLE according to required-state and available evidence.

Relevant ReasonCode values: SERVICE_ACTIVE, SERVICE_INACTIVE, SERVICE_FAILED, INTERNAL_ERROR

All collectors use structured ObservationStatus values and retain unavailable optional fields explicitly.

Graceful unavailability and limits

Requires systemd and visibility into the selected manager. It never starts, stops, restarts, reloads, enables or disables a unit.

Permissions and privacy

Permissions. The runtime account needs permission to query the relevant systemd manager.

Privacy. Unit descriptions, paths and process identifiers can reveal deployment structure; restrict audit readership.

Sanitized example

{
  "source": "systemd",
  "status": "SUCCESS",
  "severity": "INFO",
  "reason_code": "SERVICE_ACTIVE",
  "target": "example.service",
  "metadata": {"active_state":"active","sub_state":"running","main_pid":1200}
}

Synthetic example. It is not production node data.