ADSM-L

Monitoring ADSM for errors.

1997-05-19 23:55:28
Subject: Monitoring ADSM for errors.
From: Wayne Gorton <wayneg AT AU1.IBM DOT COM>
Date: Mon, 19 May 1997 23:55:28 -0400
Howdy All,
I am currently revisiting the way we monitor ADSM's activity.
Our environment is 20 nodes backing up to 1 server (all on an SP) overnight.
We use NetView to monitor the file dsmerror.log. This issues all sorts of
messages that don't need to be passed onto NetView.
The manual "ADSM for AIX: Advanced Topics" recommends monitoring the console
log instead of the dsmerror.log (but doesn't say why).
The console log is piped out to /dev/null. Is this the norm?
Is there a mechanism for pruning the console log or dsmerror.log?
It also says to monitor for specific messages & ignore the rest.
I think it would be better to take a sample of the most common messages &
filter out the messages you don't need to see. This way should ADSM issue any
new messages (in future versions) we won't be ignoring them.

What's the consensus, monitor the console log or dsmerror.log?
What does everyone else do?

I'd welcome any opinions/advise before I start scripting.

Role:                               Unix System Administrator
Style:                              The Thinking Man's Clown
Name:                               wayneg AT au1.ibm DOT com
Life:       "Imagination is more important than knowledge"   Albert Einstein
<Prev in Thread] Current Thread [Next in Thread>