No alarm on route:
list Tod Hansmann
This may actually be a silly question, but I didn't find anything in the docs that sounded like it fit the bill. Anyway, we monitor a lot of remote sites where we monitor one device with another device behind it, with another device behind it, with more devices behind that, etc. We're using route:nexthostout in bb-hosts to keep all of them from going red when the devices further down the line aren't the issue, but they still turn up yellow on the bb2 page. Is there a way to only see the device that actually went red, and not the others that require it as their route? If not, it's no deal-breaker, but it would be helpful if our alarms page wasn't covered in hosts just because a remote site's internet router went down. Tod Hansmann Network Engineer 333 South 520 West, #200 Lindon, Utah 84042 Office: XXX.XXX.XXXX <http://www.directpointe.com/>; CONFIDENTIAL COMMUNICATION: E-mails from DirectPointe may contain confidential material for the sole use of the intended recipient. If you received this e-mail in error, please delete the e-mail and all attachments. Thank you.
list Tod Hansmann
As an FYI for the archives, I think this might be doable via a NOPROPYELLOW:+conn but I can't experiment with it at the moment, so it will be left in theory for the moment =c) Tod Hansmann Network Engineer
▸
From: Tod Hansmann [mailto:user-b6e28cb93fa4@xymon.invalid]
Sent: Wednesday, October 10, 2007 9:30 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] No alarm on route:
This may actually be a silly question, but I didn't find anything in the docs that sounded like it fit the bill. Anyway, we monitor a lot of remote sites where we monitor one device with another device behind it, with another device behind it, with more devices behind that, etc.
We're using route:nexthostout in bb-hosts to keep all of them from going red when the devices further down the line aren't the issue, but they still turn up yellow on the bb2 page. Is there a way to only see the device that actually went red, and not the others that require it as their route?
If not, it's no deal-breaker, but it would be helpful if our alarms page wasn't covered in hosts just because a remote site's internet router went down.
Tod Hansmann
Network Engineer
333 South 520 West, #200
Lindon, Utah 84042
Office: XXX.XXX.XXXX
CONFIDENTIAL COMMUNICATION: E-mails from DirectPointe may contain confidential material for the sole use of the intended recipient. If you received this e-mail in error, please delete the e-mail and all attachments. Thank you.
list Tod Hansmann
Got a chance to test this, and the NOPROPYELLOW works fantastically! Tod Hansmann Network Engineer
▸
-----Original Message-----
From: Tod Hansmann [mailto:user-b6e28cb93fa4@xymon.invalid]
Sent: Thursday, October 11, 2007 9:29 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: RE: [hobbit] No alarm on route:
As an FYI for the archives, I think this might be doable via a NOPROPYELLOW:+conn but I can't experiment with it at the moment, so it will be left in theory for the moment =c)
Tod Hansmann
Network Engineer
From: Tod Hansmann [mailto:user-b6e28cb93fa4@xymon.invalid]
Sent: Wednesday, October 10, 2007 9:30 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] No alarm on route:
This may actually be a silly question, but I didn't find anything in the docs that sounded like it fit the bill. Anyway, we monitor a lot of remote sites where we monitor one device with another device behind it, with another device behind it, with more devices behind that, etc.
We're using route:nexthostout in bb-hosts to keep all of them from going red when the devices further down the line aren't the issue, but they still turn up yellow on the bb2 page. Is there a way to only see the device that actually went red, and not the others that require it as their route?
If not, it's no deal-breaker, but it would be helpful if our alarms page wasn't covered in hosts just because a remote site's internet router went down.
Tod Hansmann
Network Engineer
333 South 520 West, #200
Lindon, Utah 84042
Office: XXX.XXX.XXXX
CONFIDENTIAL COMMUNICATION: E-mails from DirectPointe may contain confidential material for the sole use of the intended recipient. If you received this e-mail in error, please delete the e-mail and all attachments. Thank you.