Retrieving the active Alert file

Seems to me to be overkill unless I am missing something.

Simply create multiple Alert files and give each some meaningful name like weekend.alrt, etc.   Make sure you save a copy of your stardard alerts file to something like standard.alrt. Then when you need your special alerts simply rename the alert file you want to use to default.alrt.  Then run hcisitectl.  When no longer needed rename standard.alrt to default.alrt and run hcisitectl again.

This could be easily scripted if need be and, INHO, much easier than traversing and editing an alert file.

As I said, maybe I am missing something here.

If on Linux you can run ‘ps -ef|grep hcimonitord’ on the prompt which will show you all occurrences of hcimonitord, per site. With this you can do the check you want; check on ‘-S’ to see for which site the specific monitor daemon is running.

For example: we have a regular check running to see if someone has activated the ’empty’ alert file; something we need to do if we have maintenance or need to stop some interfaces without the Alerts restarting them automatically. If the empty alert-file is running, then we get an email to warn us. Here a piece of the script.

if [ ps -ef|grep hcimonitord|grep “\-S overig”|grep empty|wc -l != 0 ]
then
/cldata/scripts/write_alert overig overig mond no_touch mail
fi

• This reply was modified 7 months, 1 week ago by Robert Kersemakers.