[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [hobbit] Best way to monitor static routing table entries?
- To: <hobbit (at) hswn.dk>
- Subject: RE: [hobbit] Best way to monitor static routing table entries?
- From: "Root, Paul" <Paul.Root (at) qwest.com>
- Date: Wed, 12 Nov 2008 12:48:25 -0600
- Importance: normal
- Priority: normal
- Thread-index: AclE6B0oT3msLgh2R7mwLhCE18MrQwADu4Tg
- Thread-topic: [hobbit] Best way to monitor static routing table entries?
Just write the script to parse the netstat output, then at the end
decide if it's green or not and send a message to hobbit with the 'bb'
command.
Paul Root IM/MNS Infrastructure
-----Original Message-----
From: Gregory Larkin [mailto:glarkin (at) sourcehosting.net]
Sent: Wednesday, November 12, 2008 11:00 AM
To: hobbit (at) hswn.dk
Subject: [hobbit] Best way to monitor static routing table entries?
Hello all,
I've been using Hobbit for a few years now, and it has always worked
really
well for me. Lately, I've added some more tests to certain servers, and
one
thing I'd like to do is detect the presence/absence of some static
routes
that are configured on a RHEL4 Linux box.
I could write a script that greps the output of "netstat -rn" and
redirects
it to a file. Hobbit could monitor the content of the file to make sure
it
matches some predefined template, I suppose, but is there a more elegant
way?
I checked the BB script archive, and I found the bb-route extension, but
it's either not the right solution or too complicated for what I want to
do.
Any suggestions?
Thank you,
Greg
Greg Larkin
Managing Member
SourceHosting.net, LLC
PO Box 1013
Hollis, NH 03049 US
glarkin (at) sourcehosting.net
http://www.linkedin.com/in/greglarkin
To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk
This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.