486 |
|
|
487 |
Recipients in the global and in the local lists are alerted when |
Recipients in the global and in the local lists are alerted when |
488 |
an failed, recovery or changed event occurs. If the same email |
an failed, recovery or changed event occurs. If the same email |
489 |
address is in the global and in the local list, monit will still |
address is in the global and in the local list, monit will send |
490 |
only send one alert. Local (per service) defined alert email addresses |
only one alert. Local (per service) defined alert email addresses |
491 |
override global addresses in case of a conflict. Finally, you may |
override global addresses in case of a conflict. Finally, you may |
492 |
choose to only use a global alert list, a local per service list |
choose to only use a global alert list, a local per service list |
493 |
or both. |
or both. |
503 |
|
|
504 |
=over 4 |
=over 4 |
505 |
|
|
506 |
=item SET ALERT mail-address [{events}] [MAIL-FORMAT {mail-format}] |
=item SET ALERT mail-address [{events}] [MAIL-FORMAT {mail-format}] [REMINDER number] |
507 |
|
|
508 |
=back |
=back |
509 |
|
|
523 |
|
|
524 |
=over 4 |
=over 4 |
525 |
|
|
526 |
=item ALERT mail-address [{events}] [MAIL-FORMAT {mail-format}] |
=item ALERT mail-address [{events}] [MAIL-FORMAT {mail-format}] [REMINDER number] |
527 |
|
|
528 |
=back |
=back |
529 |
|
|
700 |
|
|
701 |
=head2 Setting a global mail format |
=head2 Setting a global mail format |
702 |
|
|
703 |
Finally, it is possible to set a standard mail format with the |
It is possible to set a standard mail format with the |
704 |
following global set-statement (keywords are in capital): |
following global set-statement (keywords are in capital): |
705 |
|
|
706 |
=over 4 |
=over 4 |
717 |
set mail-format { from: monit@foo.bar.no } |
set mail-format { from: monit@foo.bar.no } |
718 |
|
|
719 |
|
|
720 |
|
=head2 Setting a error reminder |
721 |
|
|
722 |
|
Monit by default sends just one error notification when the |
723 |
|
service failed and another one when it has recovered. If you want |
724 |
|
to be notified more then once in the case that the service remains |
725 |
|
failed, you can use reminder option of alert statement (keywords |
726 |
|
are in capital): |
727 |
|
|
728 |
|
=over 4 |
729 |
|
|
730 |
|
=item ALERT ... [WITH] REMINDER [ON] number [CYCLES] |
731 |
|
|
732 |
|
=back |
733 |
|
|
734 |
|
For example if you want to be notified each tenth cycle when the |
735 |
|
service remains failed, you can use: |
736 |
|
|
737 |
|
alert foo@bar with remainder on 10 cycles |
738 |
|
|
739 |
|
If you want to be notified each failed cycle, you can use: |
740 |
|
|
741 |
|
alert foo@bar with remainder on 1 cycle |
742 |
|
|
743 |
|
|
744 |
=head2 Setting a mail server for alert messages |
=head2 Setting a mail server for alert messages |
745 |
|
|
746 |
The mail server monit should use to send alert messages is |
The mail server monit should use to send alert messages is |
2787 |
I<minute(s)>, I<hour(s)>, I<day(s)>, I<space>, I<inode>, I<pid>, |
I<minute(s)>, I<hour(s)>, I<day(s)>, I<space>, I<inode>, I<pid>, |
2788 |
I<ppid>, I<perm(ission)>, I<process>, I<file>, I<directory>, |
I<ppid>, I<perm(ission)>, I<process>, I<file>, I<directory>, |
2789 |
I<device>, I<size>, I<unmonitor>, I<rdate>, I<rsync>, I<data>, |
I<device>, I<size>, I<unmonitor>, I<rdate>, I<rsync>, I<data>, |
2790 |
I<invalid>, I<exec>, I<nonexist>, I<policy> and I<failed> |
I<invalid>, I<exec>, I<nonexist>, I<policy>, I<reminder> and |
2791 |
|
I<failed> |
2792 |
|
|
2793 |
And here is a complete list of B<noise keywords> ignored by |
And here is a complete list of B<noise keywords> ignored by |
2794 |
monit: |
monit: |