Où sommes nous ?

Domestik's alerts

Kinds of alerts

Alerts can be generated by several sources :

by Domestiks server itself : for example, when an host hasn't sent any data for a period of time exceeding its inactivity threshold.
by probes themselves : typically, hardware can generate alerting.
while probes figures exceed its own threshold : while system load is greater than number of available CPUs.
for notifying about internal problem : for example, if a probe has crashed (useful to debug you own probe ... or to submit a bug report if a problem occurred with a 3rd party one).

probes's life cycle

Some alerts will resolve automatically

Some alerts reflect a temporary situation and, consequently will disappear automatically when alert's cause is corrected.

CPU load, resource's usage, temperature, processes tracking, ... are example of auto-resolving cause of alert.

Alerts needing manual acknowledgment

Some alerts have to be manually removed from alert list : disk smart reporting, probe's crashes ...

Notez-bien

An alert is created every time a probe crashed : consequently, in case of issue, ensure a probe crash only once otherwise you will spam your alert list.

As soon as you're logged, a "remove button" appears in "current alert list" tab.

Visitez : La liste de nos voyages Nos sorties Ski et rando	Copyright Laurent Faillie 2001-2024 N'oubliez pas d'entrer le mot de passe pour voir aussi les photos perso.	Contactez moi si vous souhaitez réutiliser ces photos et pour les obtenir avec une plus grande résolution.
Visites durant les 7 derniers jours au total.

Vous pouvez laissez un commentaire sur cette page.