It's a good place to start. how many e-mails a day?
start by creating a mailing list for these messages, have one of the addresses
be a read-only archive of the messages
The next step is to create an address that's a script that recevies these
messages and keeps the most recent of each type into a status web page
later on we can add smarts to this last item so that we only get alerted when
something fails (or we don't get the expected success message in a reasonable
time)
But for the moment, in the interest of getting the core functionality (the build
process) up and running, all we need to do is step 1.
This doesn't mean that if someone has time or interest to do something nicer,
they shouldn't do it, but more a matter of "what's the minimum that Rainer and
Adiscon need to do to make things functional"
David Lang
On Mon, 15 Jun 2015, Rainer Gerhards wrote:
Hi all,
in my current Adiscon environment, I simply send mail to indicate
error or success of the various scipts. This doesn't seem to be the
right way for the packaging project (rpp). How do we intend to handle
that?
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
