Really, honestly, im not trying to belabor a point here, but you need to be
careful as the ping only runs every 5 minutes, so even if you could get this
alerting to work, the link would have to be slow during a ping cycle. So it
could possible be slow for 4 minutes, recover, and the page wouldn't happen,
as the ping time would be ok. Assuming the client saw the slowness during
those 4 minutes via other methods, they would then question why hobbit
didn't see it.
Same thing hapens to me with spikes in network traffic between polling
periods, I don't see them.
With MRTG, you can shorten the time to 1 minute. MRTG integration with
hobbit isn't too hard, so thats probably the route you should go.
-Jeff
On 1/13/06, Charles Jones <user-e86b4aeade4e@xymon.invalid> wrote:
Deal, Richard wrote:
Sounds like they need to through in MRTG and go red when the traffic is
high on the link.
And then throw in things like
bb-ospf.pl to check that ospf is not flapping over the link
bb-xsnmp.pl to check out the routers at each end and the interfaces
Yeah I'm aware of the existance of bb-mrtg.pl, although I have never set
it up. I guess I was hoping that Hobbit could natively support ping testing
rather than having to install mrtg and hack stuff in. Its sort of confusing
for a newbie when you are showing them the ropes of Hobbit and start
bringing external scripts into the mix (especially ones that require
modifying before they will work).
you can also use http to a reliable server on the remote side as part of
the link test. Just make the http test for the link dependent on the router
and the conn test to the web server.
That won't work in this case as all of the companies servers are in a
CoLo, Hobbit is running at the CoLo, and they want to test the T1 link at
the office from the CoLo (there are no servers on the other side of the
office T1 to do a test against), and even if there was, it still would not
give them a heads-up to the T1 being slow/saturated, as Hobbit only alerts
when the conn test outright fails.
-Charles
*From:* Charles Jones [mailto:user-e86b4aeade4e@xymon.invalid <user-e86b4aeade4e@xymon.invalid>]
*Sent:* Friday, January 13, 2006 1:01 PM
*To:* user-ae9b8668bcde@xymon.invalid
*Cc:* user-9ae1c8bba037@xymon.invalid
*Subject:* [hobbit] conn alerts based on ping time
I'm helping someone set up Hobbit at their company, and they want to
monitor the status of a remote office T1 link. Of course Hobbit can tell
them if the link goes totally down, or you can ignore bad pings with
"badconn", but they want to know when the link is *slow*, as they often
have periods of time when the pings are not dropped, but instead taking 1-3
seconds (instead of <100ms like normal).
Is there any chance that Hobbit will soon support comparing the ping
replies to specifiied values for green, yellow, and red?
Somethign like:
1.2.3.4 myhost.com # conn:200:500
This would make myhost.com's conn test go yellow if the ping was between
200 and 500ms, and red if it was over 500ms.
Since hobbit already graphs the numeric values of the ping replies, this
seems like it would be fairly easy to add?
-Charles