more systemd unit check posibilities
This commit is contained in:
@@ -209,8 +209,7 @@ Here the warning is below 180 days and below 30 days is critical by default.
|
||||
|
||||
### Check for Systemd Service Status
|
||||
|
||||
To check if a daemon or service has been successfully started by `systemd` configure:
|
||||
|
||||
To check if a daemon or service has been successfully started by `systemd` configure a custom service using the `st-agent-awi-lx-service-active` template:
|
||||
|
||||
```
|
||||
icinga2::custom_service:
|
||||
@@ -227,6 +226,20 @@ The `service_names` variable needs to contain one or more name of `systemd` serv
|
||||
|
||||
You can create multiple of these checks.
|
||||
|
||||
Alternatively a more detailed configuration of a systemd unit state check can be done with the `st-agent-lf-systemd-unit` template:
|
||||
|
||||
```
|
||||
icinga2::custom_service:
|
||||
'Last Puppet Run':
|
||||
template: 'st-agent-lf-systemd-unit'
|
||||
vars:
|
||||
systemd_unit_unit: 'pli-puppet-run'
|
||||
systemd_unit_activestate: ['active', 'inactive']
|
||||
systemd_unit_unitfilestate: 'static'
|
||||
criticality: 'A'
|
||||
```
|
||||
|
||||
|
||||
### External Connection Checks (Active Checks)
|
||||
|
||||
For this we have fully custom service checks.
|
||||
|
||||
Reference in New Issue
Block a user