[PMX:#] Advice on notification setup
Collins, Steve
Steve.Collins at industry.gov.au
Mon Aug 30 07:49:39 CEST 2004
I have a set of hosts/services which I want checked 24x7, which is easy. However, I want the notifications to go to a certain Contact Group (emails only for my team) during workhours and to a different Contact Group (SMS only for my team) in nonworkhours. Based on this theory, I then want host and service escalations based on workhours/nonworkhours division of notifications.
Here's a theoretical grid (many more services, but this is indicative):
Service Group Type Interval (min) Notification Period
check_http webdev email 0,15,30,45,60,etc. workhours
webdev sms 0,60,120,etc. nonworkhours
servicedesk email 15 only 24x7
managers email 30,90,etc. workhours
managers sms 30,90,etc. nonworkhours
I have Contact Groups established that will cover the splitting of notifications by email and sms where the same group (of people) needs different notification types based on time of day, but I'm a bit foggy on how I should approach the escalations for greatest efficiency.
Any and all advice appreciated and TIA.
Steve
--
Stephen Collins
Web Development Section
eBusiness Division
__________________________________________________
Department of Industry, Tourism and Resources
Level 12, 20 Allara Street, Canberra City ACT 2600
GPO Box 9839, Canberra ACT 2601
E steve.collins at industry.gov.au
P +61 2 62137193
C +61 410 680722
F +61 2 62136227
**********************************************************************
The information contained in this e-mail, and any attachments to it, is
intended for the use of the addressee and is confidential. If you are not the intended recipient you must not use, disclose, read, forward, copy or retain any of the information. If you have received this e-mail in
error, please delete it and notify the sender by return e-mail or telephone.
The Commonwealth does not warrant that any attachments are free from viruses or any other defects. You assume all liability for any loss, damage or other consequences which may arise from opening or using the attachments.
***********************************************************************************
More information about the Users
mailing list