Page History

...

How Are Active Checks Performed?

Image Removed

Active checks are initiated by the check logic in the Shinken Enterprise daemon. When Shinken Enterprise needs to check the status of a host or a check, it will execute a plugin and show the information about what needs to be checked. The plugin will then check the operational state of the host or check and report the results back to the Shinken Enterprise daemon. The scheduler daemon will process the results of the host or check and take the appropriate action if necessary (e.g. send notifications, ask for event handlers, etc).

Image Added

When Are Active Checks Executed?

...

Passive checks are also used when configuring :ref:`distributed <advanced/distributed>` or :ref:`redundant <advanced/redundancy>` monitoring installations.

How Passive Checks Work

...

 

Here's how passive checks work in more detail. An external application checks the status of a host or check. The external application writes the results of the check to the external command named pipe (a named pipe is a "memory pipe", so there is no disk IO involved). Shinken Enterprise reads the external command file and places the results of all passive checks into a queue for processing by the appropriate process in the Shinken Enterprise cloud. Shinken Enterprise will get results each second and scan the check result queue. Each check result that is found in the queue is processed in the same way - regardless  whether the check was active or passive. Shinken Enterprise may send out notifications, log alerts, etc. depending on the check result information. The processing of active and passive check results is essentially the same. This allows for seamless integration of status information from external applications with Shinken Enterprise.

Image Added

 

 

 

Enabling Passive Checks

In order to enable passive checks in Shinken Enterprise, you'll need to do the following:

...