which alert file is being used

This topic has 5 replies, 4 voices, and was last updated 14 years, 9 months ago by Russ Ross.

Creator

Topic
July 21, 2011 at 6:32 pm #52609
Kevin Scantlan
Participant
How can you tell what alert file is being used by the monitor daemon? I know the log tells you when the monitor daemon first comes up, but it’s been a few days and the log has cycled out. I want to do a query and have the system tell me.

Thanks.
Creator

Topic

Viewing 4 reply threads

Author

Replies
- July 22, 2011 at 7:56 am #74844
  Robert Kersemakers
  Participant
  If you’re on Unix, you can do a ‘ps -ef |grep hcimonitord’ which show all the monitor daemons that are running:
  
  Code: 5.5_orbis:/cldata/scripts> ps -ef |grep hcimonitor hci 1612 1 0 Jun 9 ? 250:43 hcimonitord -S upgrade hci 25139 1 0 Jul 9 ? 302:22 hcimonitord -S orbis hci 2939 2624 0 09:48:35 pts/ta 0:00 grep hcimonitor hci 16058 1 3 May 31 ? 554:21 hcimonitord -S upgrade hci 22700 1 0 Jul 18 ? 26:15 hcimonitord -cl orbis_empty.alrt -S test hci 1506 1 0 Jun 9 ? 225:26 hcimonitord -S test
  
  The -cl option will show the alert-file that is in use. If there is no -cl option mentioned, then default.alrt is used.
  
  Not sure how you can see this in Windows: it doesn’t show in the Taskmanager.
  
  Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands
- July 22, 2011 at 1:10 pm #74845
  Charlie Bursell
  Participant
  Much simplier 😀
  
  Unless you specify differently you will always use the default.alrt file
  
  I teach that you should always use the default so as not to use the wrong file by mistake. If you use several different Alert files, e.g., weekdays, nights, weekends, etc., simplly copy the one you wish to use to default.alrt and restart the daemon.
  
  This way if someone has to restart the daemon for another reason they don’t restart with the wrong Alerts file
- July 22, 2011 at 1:23 pm #74846
  Kevin Scantlan
  Participant
  We use the default.alrt by default. However, there are occasions, like when we have a planned outage, that we don’t want a subset of the alerts not to be triggered. So, I schedule a script to run that puts in an alert file with certain alerts removed when the outage is to begin, then schedule a script to run the puts the default back in when the outage is over.
- July 22, 2011 at 2:41 pm #74847
  Robert Kersemakers
  Participant
  Do you really need to restart the daemon after copying to default.alrt? Isn’t this similar to ‘touching’ the default.alrt?
  
  Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands
- July 22, 2011 at 8:25 pm #74848
  Russ Ross
  Participant
  We use the default.alrt file but configure different alerts within that file for weekday, weeknight, and weekend.
  
  Almost all our alerts call a argument driven script that pages/emails and cycles the interface.
  
  To help with toggling off any alerts for a given thread our alert script checks if we have created a file called $HCISITEDIR/Alerts/$threadName.off.
  
  This gives us control to turn alerts on/off for any combination of threads we desire.
  
  Our alert script also concatenates an entry to $HCISITEDIR/$threaName.log showing:
  
  – what alert got triggerred
  
  – when it got triggerred
  
  – the action taken
  
  – who got email/paged
  
  An additional enhancement on the wish list is to have it concatenate the information entry to an all_alerts file so they are consolidate all in one file in addition to the individual theard logs.
  
  Russ Ross
  RussRoss318@gmail.com
Author

Replies

Viewing 4 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.