Emailed notices: Warnings versus Alerts

Last updated:

Preventing repeated warnings about known issues

As the client software makes its hourly run, the results are sent back to the server for processing.

The Watchman Monitoring servers take in the reports and generate emails.

Warning Emails are sent the first time a problem is reported.

Examples of events which would lead to warning emails being sent include:

  • Time Machine not being able to run in the desired interval (7 days by default).
  • Hard drives which become too full (90% by default, adjustable per-volume).
  • Cloud backups failing to complete
  • Specified applications not running.
  • Disk i/o errors. 

Warning emails serve to inform and remind Subscribers that there is a problem on a given computer.

 

Alert Emails are sent when a one-time event happens.

Examples of events which would trigger an alert include:

  • Reboot notices (if requested)
  • Kernel Panic reports
  • Disabling of a backup system

As a rule of thumb, if a problem might persist for a period of time, a warning will be sent. If a problem happens and is over, an Alert will be sent.

 

Muting, and Alerts vs Warnings

Regardless of the kind of email, Watchman Monitoring is designed to let IT professionals know when there is work to be done. Warning emails repeat daily for as long as an issue is present, or until Muted.

Alerts, on the other hand, are over once they have happened, and so are not subject to Muting. To mute these alerts would mean that subsequent repeated errors might be rolled up into one issue, despite being separate events. 

Should an alert be undesired, the related plugin can be ignored.

 

Read more about muting in this article:

Preventing repeated warnings about known issues

 


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.