You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 13, 2020. It is now read-only.
In pager emails, if you test nagios-herald with, for instance, the included check_disk.CRITICAL test, you get the following output in the body of the email:
CRITICAL for 0d 0h 5m 12s (was CRITICAL) after 3 / 3 checks
Normally, the host_info section is shown on the first line. Instead, state_info takes up the first line, and the hostname information is displayed in the subject of the email instead. This may cause problems because 1) different carriers may have different ways of incorporating SUBJECT headers into SMS messages, 2) which leaves us with less fluidity as to how we want our messages to be formatted (unless we have nagios-herald send out a blank subject), and 3) once the host_info section is fixed to show up in the body of the pager email, there will be redundancy in the SMS due to displaying the hostname in both the subject and body.
The text was updated successfully, but these errors were encountered:
In pager emails, if you test nagios-herald with, for instance, the included check_disk.CRITICAL test, you get the following output in the body of the email:
Normally, the host_info section is shown on the first line. Instead, state_info takes up the first line, and the hostname information is displayed in the subject of the email instead. This may cause problems because 1) different carriers may have different ways of incorporating SUBJECT headers into SMS messages, 2) which leaves us with less fluidity as to how we want our messages to be formatted (unless we have nagios-herald send out a blank subject), and 3) once the host_info section is fixed to show up in the body of the pager email, there will be redundancy in the SMS due to displaying the hostname in both the subject and body.
The text was updated successfully, but these errors were encountered: