On Thu, Sep 01, 2005 at 10:27:21PM, Henrik Stoerner wrote:
On Thu, Sep 01, 2005 at 03:42:26PM -0400, Asif Iqbal wrote:
On Mon, Aug 29, 2005 at 10:13:05AM, Asif Iqbal wrote:
Seems like BBALPHAMSG is being ignored by hobbit-4.1.1 server. I have a
I was wrong. BBALPHAMSG is still part of hobbit-4.1.1 but it only keeps
the status logs. Is that mean all msgs files are coming in as data log?
In that case what variable do I use with my ALERT scripts to scan msgs
data?
I've lost track of what you want to do.
BBALPHAMSG contains the text in a Hobbit "status" message, which is the
only thing that can trigger an alert.
Are you referring to the data for a "msgs" status column ? The Hobbit
I think so. In hobbit-4.0.4 and below, if a client has the word 'core
dump' in the WARNING line of its /var/adm/messages file I would ignore
that ALERT. But since hobbit-4.1.1 it is failing.
So I think you already answered why it is failing.
Thanks for building such a good tool which does exactly what it suppose to do,
does it well.
client does not implement data collection for the "msgs" column, so that can never trigger an alert. Until I've found a good way of doing
system log monitoring, you can use some of the BB add-on scripts from
deadcat.net - these should generate a normal status message and hence
show up in the normal way for your alerts (including BBALPHAMSG).
Henrik
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
"..there are two kinds of people: those who work and those who take the credit...try
to be in the first group;...less competition there." - Indira Gandhi