[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Real Notification Requirements
On Tue, Mar 28, 2006 at 05:02:25PM +0200, Shane Kerr wrote:
> Perhaps it would be better to focus on adding a subscription mechanism
> to SYSLOG?
Certainly an option. Having a subcription mechanism is actually for me
an important feature. Some 12 years ago, we hacked our central syslog
daemon to actually ship syslog messages once you connected to it and
it was a lovely hack which we used a lot (since it makes access to
syslog message real simply for programs).
On the classification question: I think you can put anything into
syslog, so the distinction between syslog messages, configuration
change notifications, or SNMP notifications is kind of artificial.
In fact, it seems popular in many operational environments to have
SNMP notification receivers which simply write to syslog, probably
because there are also pretty nice syslog readers that can trigger all
sorts of actions when they discover certain input patterns.
If we do an interim, it would be valuable to get some syslog experts
there as well so that we can evaluate whether structured syslog and
syslog enhancements will actually solve the problem.
/js
--
Juergen Schoenwaelder International University Bremen
<http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany
--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>