My thinking at this point is to write a perl script that filters emails
into known categories (folders, in my mind) and then gives them to
either a trouble ticket system or a web-based bulletin board kind of
thing. All unknowns will fall into their own high-priority folder.
Messages from the outside (to root, overseer, those kinds of accounts)
tend to be security related - so they'll probably default into a
high-priority security folder. While I'm at it, I'll probably also take
the logs that get rolled over once a week and publish them in part as a
digest.
It was suggested I look into Big Brother for monitoring multiple
systems, req-ng, Remedy, and Globetrotter as a trouble ticket systems,
and "tin" and INN for the news side of things.
I had one person suggest that I get rid of email altogether - nice idea,
especially if you take it out of context.
Rudy, I've forwarded all of my responses to you.
Thanks to:
Francois
Jim
Danny
Jochen
Karl
Matt
The original question:
"adam r. christopher" wrote:
>
> We have a number of DU, Solaris, HPUX, and NT servers that routinely
> generate error/info messages that are then sent as email to various
> accounts. My question is, how do you handle/manage/organize all of
these
> messages?
>
> These messages range from the inocuous to the panic-inducing
> (warnings about user quotas, undeliverable mail, system faults, system
> resets, password expiration warnings, etc. etc.), so prioritizing them
is,
> well, a priority.
>
> Having all of the mail go to a single account on a given machine
probably
> will not work for various reasons. I'm thinking about creating a
bulletin
> board style solution, or maybe there's a trouble ticket product out
there
> that I'm unaware of. I'd like to know how others are handling this
kind of
> thing before I get too far ahead.
>
> Thanks, I'll summarize.
>
> -adam
Received on Mon Mar 08 1999 - 22:17:11 NZDT