Passive Check Configuration Defaults
- Sebastian Koch
Owned by Sebastian Koch
Passive service checks depend on an external source updating the service with status information. Such passive service checks are used in various cases:
- SONARGATE, all status information is delivered to the SONARPLEX as passive service check
- Distributed Monitoring and Integration Interfaces, services from the satellites are created as passive service checks at the NOC
- SonarTCPd, all status information is delivered to the SONARPLEX as passive service check
The following settings specify the details of such passive service checks, especially for the ones which are created automatically, like in Distributed Monitoring and Integration Interfaces.
On this page:
Passive Check Settings
Below are the different settings explained.
| Setting | Description |
|---|---|
| Default service output upon transfer problems | Alert message that should be shown if no status information was received until the Freshness Interval |
| Default service state upon transfer problems | Service state that should be used for the service if no status information was received until the Freshness Interval |
| Retain state for outdated services | When enabled, service which are outdated won't change into an UNKNOWN state but will instead retain the current state |
| Notification Interval | Default notification interval for newly created passive service checks. Applies only for automatically created services. |
| Notification options | For which states should a notification be sent:
|
The following macros are not currently supported in the footer:
- style