Bill, While it's not exactly what he was looking for, I do see some value in creating a hierarchy like you are suggesting. If anything, it would reduce the multiplicity of alarms that is created by the individual services when a server goes down.
Thanks, Tony -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of William W. Fisher Sent: Wednesday, January 11, 2006 1:50 PM To: InterMapper Discussion Subject: Re: [IM-Talk] Question about monitoring objects - object linking (same object on several maps) On Jan 11, 2006, at 10:24 AM, Steven Good wrote: > Lets say we have a map called "Email Services" and another map "File > Services" on these maps are the individual service probes for their > components, along with the devices/servers. > > We have several services that may share the same server. > > So email and file_services also share server_A, and we need to take > server_A down for maintenance. If we has a probe for server_A on both > maps, we would have to pre-acknowledge it on both maps. > > By object linking, I am asking if we acknowledge server_A on the email > map, that it would also be acknowledged on the file_services map? At > least that is the way we would like it to work. I am assuming that these "object links" would be uni-directional? That is, if you acknowledge server_A, then email_service_A and file_service_A would be acknowledged as well, but if you acknowledge email_service_A, this does not affect server_A or file_service_A. To put it another way, the relationship is equivalent to parent/child? server_A is the parent. It has two children: email_service_A and file_service_A. Regards, Bill Fisher Dartware, LLC ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [EMAIL PROTECTED] ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [EMAIL PROTECTED]
