We are on the same page then. I don't think I would ask Hobbit to do
this for very many devices. I handle 100 traps per second in Netcool,
and I am just getting started. But I love what Hobbit provides for
monitoring the tool servers themselves -- without relying on anything on
those same servers in order to function.
GLH
-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid]
Sent: Tuesday, July 17, 2007 8:33 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Hobbit not recognizing certain tests?
On Tue, Jul 17, 2007 at 08:07:31AM -0500, Hubbard, Greg L wrote:
Being familiar with both Netcool and Hobbit, I would never consider
replacing Netcool trap management with Hobbit. Netcool processes
traps in "near real time" and scales quite large. Hobbit does not
provide real time monitoring (default is 5 minute samples, with 1
minute screen updates).
There is nothing inherent in Hobbit that prevents it from doing
real-time handling of events. Hobbit processes events as soon as it is
told about them; the fact that some types of information is only checked
once every 5 minutes is not something that necessarily applies to
everything Hobbit monitors.
I havent looked at Andy's trap script, but if I were to implement SNMP
trap handling in Hobbit, I'd start off with snmptrapd from the Net-SNMP
tools - this receives snmp traps, and can be configured to do
"something" when a trap arrives. That "something" would then be a
script/utility that grabs the hostname and trap type from the trap
information, and feeds that into Hobbit as a status update. That will
give you an immediate alert, and a status change in the Hobbit display
if you use the "Critical systems" view which is dynamically generated.
I'm not throwing rocks at Netcool <grin> but I just want to make it
clear that Hobbit can be as real-time as you want it to - it's only a
matter of feeding it data as quickly as you possible.
Regards,
Henrik