ADSM-L

Re: Monitoring, and Generating alerts from ADSM.

2000-09-11 09:20:53
Subject: Re: Monitoring, and Generating alerts from ADSM.
From: Shekhar Dhotre <Shekhar.Dhotre.B AT BAYER DOT COM>
Date: Mon, 11 Sep 2000 09:21:00 -0400
I  have written some shell scripts for the same puropse , i will be for warding
to them on request to
perticular person.

shekhar




"DDA.RFC-822=ADSM-L AT VM.MARIST DOT EDU/P=Internet/A= /C=us" on 09/10/2000 
04:49:37 AM
Please respond to "DDA.RFC-822=ADSM-L AT VM.MARIST DOT EDU/P=Internet/A= /C=us" 
@ X400
To: "DDA.RFC-822=ADSM-L AT VM.MARIST DOT EDU/P=Internet/A= /C=us"@X400
cc:

Subject: Re: Monitoring, and Generating alerts from ADSM.

We have some Perl scripts which query the activity logs and report on a
bunch of things, like;
* Tape requests (our Silo fillith over)
* successful/missed scheduled sessions
* Summaries
* System alerts

Most things get emailed to the appropriate person. Redirecting to a logging
server wouldnt be too much of a hassle, I wouldn't think.

Cheers, Suad
--
On Fri, Sep 08, 2000 at 09:56:45AM -0700, Daniel Swan/TM wrote:
On Fri, Sep 08, 2000 at 09:56:45AM -0700, Daniel Swan/TM wrote:
> My org has determined that they'd like to incorporate ADSM into our existing
> alert infrastructure.   I figure it's a matter of parsing the event log,
> formatting the
> information, and writing it to a logfile.  The logfile is then read by a
> daemon, and
> forwarded to the Alert/Logging server.  Failed/missed backups will result in
> a late-nite page.
> (Oh goody!).
>
> Before I go about doing this though, I'd like to know about methods you
> folks have
> used for monitoring ADSM, how it is architectured, and any code you'd care
> to share.
>
> No sense re-inventing the wheel.
>
> Best regards,
> Dan.
<Prev in Thread] Current Thread [Next in Thread>