...
Checks actifs
Introduction
Shinken Enterprise is able to monitor hosts and checks in two different ways: actively and passively. Using Active checks is the most common method for monitoring hosts and checks. The main features of actives checks are the following:
- Active checks are initiated by the Shinken Enterprise poller process
- Active checks run on a regular scheduled basis
How are active Checks performed?
est capable de superviser des hôtes de 2 façons différentes :activement ou passivement . L'utilisation des checks actifs est la plus courante. Les caractéristiques principales des checks actifs sont les suivantes :
- les checks actifs sont initiés par le poller Shinken Enterprise
- ils sont lancés à intervalle régulier
Comment sont réalisés les checks actifs?
Les checks actifs sont initiés par la logique définie dans les démons dans Shinken Enterprise . Lorsque Shinken Enterprise doit vérifier les statut d'un hôte, il lance un plugin et présente les informations sur ce qui doit être vérifié. Le plugin va alors vérifié l'état de l'hôte et remonté le résultat ver le démon Shinken Enterprise . Le démon scheduler va traiter le résultat et lancer les actions appropriées si nécessaire (e.g. envoi de notifications, 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). |  |
...
Quand sont lancés les checks actifs?
Ils sont exécutés:
- à intervalles réguliers, tel que défini dans le paramétrage du check (
Active check are executed:
- At regular intervals, as defined by the "check_interval" and et "retry_interval" options in your host and check definitions
- On-demand as needed
- )
- à la demande
Si un hôte est dans l'état "HARD", il sera vérifié activement selon la définition dans le Regularly scheduled checks occur at intervals equaling either the "check_interval" or the "retry_interval" in your host or check definitions, depending on what type of state the host or check is in. If a host or check is in a HARD state, it will be actively checked at intervals equal to the "check_interval" option. If it is in a SOFT state, it will be checked at intervals equal to the retry_interval option.
On-demand checks are performed whenever Shinken Enterprise sees a need to obtain the latest status information about a particular host or check. For example, when Shinken Enterprise is determining the reachability of a host, it will often perform on-demand checks of parent and child hosts to accurately determine the status of a particular network segment.
Passive checks
Introduction
In most cases you'll use Shinken Enterprise to monitor your hosts and checks using regularly scheduled active checks. Active checks can be used to "poll" a device or check for status information as often as needed. Shinken Enterprise also supports a way to monitor hosts and checks passively instead of actively. They key features of passive checks are the following:
- Passive checks are initiated and performed by external applications/processes
- Passive check results are submitted to Shinken for processing
The major difference between active and passive checks is that active checks are initiated and performed by Shinken Enterprise, while passive checks are performed by external applications.
...
. Si il est dans un état "SOFT" , il sera vérifié selon la définition dans "retry_interval".
Le lancement à la demande peut s'effectuer sans aucun contrainte, lorsqu'on a besoin de connaître le tout dernier état d'un hôte.
Checks passifs
Introduction
Shinken Enterprise permet également de superviser les hôtes de façon passive. Les caractéristiques principales des checks passifs sont les suivantes:
- les checks passifs sont lancés par des applications ou process externes
- les résultats sont envoyés au démon Shinken Enterprise pour traitement
La principale différence avec les checks actifs réside donc dans son lancement externe.
Usages des checks passifs
les checks passifs sont utiles dans les cas :
- checks asynchrones part
Passive checks are useful for monitoring checks that are:
- Asynchronous by nature, they cannot or would not be monitored effectively by polling their status on a regularly scheduled basis, like backup or batchs
...
- Submitting check results that happen directly within an application without using an intermediate log file(syslog, event log, etc.).
How Passive Checks Work
Here's how passive checks work in more detail.
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. |  |
Enabling Passive Checks
In order to enable passive checks in Shinken Enterprise, you'll need to do the following:
...
If you want to disable passive checks for just a few hosts or checks, use the "passive_checks_enabled" directive in the host and/or check definitions to do so.
Submitting Passive check Results
You can look at the Enable webservice for passive checks about how to send external checks to the receivers.
Passive Checks and Host States
Unlike with active host checks, Shinken Enterprise does not (by default) attempt to determine whether or host is DOWN or UNREACHABLE with passive checks. Rather, Shinken Enterprise takes the passive check result to be the actual state the host is in and doesn't try to determine the hosts' actual state using the reachability logic . This can cause problems if you are submitting passive checks from a remote host.
...