[hobbit] Well, duh! I didn't know Hobbit/rrdtool did that!
Yeah, that is great and you can do more with the time scale and size in the URL. With less than a minute of editing the URL, I can print off a monthly CPU chart that I used to spend an hour creating in Windows Excel.
Thomas Kern 301-903-2211
----- Original Message ----- From: Haertig, David F (Dave) <haertig at avaya.com> To: hobbit at hswn.dk <hobbit at hswn.dk> Sent: Sun Jun 03 18:47:51 2007 Subject: [hobbit] Well, duh! I didn't know Hobbit/rrdtool did that!
After messing around and messing around trying to set graph timeframes and vertical axis limits, I just had a duh! moment. You don't need that.
Those little magnifying glass icons? Yeah, I had clicked on them before expecting to zoom in on the graph. But it never zoomed in ... it just showed the same graph again on a seperate webpage. I figured it was some broken feature. My duh! moment just came when I accidently drug my mouse cursor over part of the "non zoomed" graph and noticed, "Hey! I wonder why it highlighted only that small portion of the graph?!" Release the mouse button and it becomes very evident why. DUH!!!
How is it possible for me to have been so stupid?! :-o
Odd ack problem
I have a machine that went red for CPU
It generated an "cookie" of 371004 , and paged reciepent1. It was then ACK'd for 8 hours. CPU recovered after 2 hours, then went red again. This generated a new "cookie" of 344975, which we could no longer ACK because in the hobbitdboard it had the "old" ack data and time. This new "cookie" then escalated (because we could not ack this event)
Is there some logic I need to look at in do_alert where something recovers and can't be ack'd again?
-Sean
I am replying to my own message so if people search the archive they can figure this out faster than I did.
This was occurring because the event went green --> red --> yellow --> red And I did not have yellow set as a "okcolors" so the logic for A_OK in hobbitd was never called (clear the ack message) - but the logic for state change was (change cookie)
Dunno why you would want it to not clear the ack message but generate a new cookie, but adding yellow to the okcolors fixed it.
Thanks everyone for the suggestions
-Sean
-----Original Message----- From: Sean R. Clark [mailto:sclark at nyroc.rr.com] Sent: Monday, June 04, 2007 9:43 AM To: 'hobbit at hswn.dk' Subject: ACK problems
Odd ack problem
I have a machine that went red for CPU
It generated an "cookie" of 371004 , and paged reciepent1. It was then ACK'd for 8 hours. CPU recovered after 2 hours, then went red again. This generated a new "cookie" of 344975, which we could no longer ACK because in the hobbitdboard it had the "old" ack data and time. This new "cookie" then escalated (because we could not ack this event)
Is there some logic I need to look at in do_alert where something recovers and can't be ack'd again?
-Sean
participants (2)
-
sclark＠nyroc.rr.com
-
Thomas.Kern＠hq.doe.gov