[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Netconf Event Message as Working Group Document

Phil Shafer wrote:


Andy Bierman writes:

Anyone one the list with an opinion, please speak up!


Hey, that's me!! ;^)

I do feel that we need more than syslog.  In particular, I want
to be able to say "give me all the events from the last 20 minutes
that relate to interface fe-1/2/3.0".  So I need to be able to
ship specific fields in addition to the message text.  Consider:

   <notification>
     <time seconds=234532455432345>Oct 18 16:01:37</time>
     <tag>RPD_RSVP_NBRUP</tag>
     <hostname>farmer-john</hostname>
     <process pid=2958>rpd</process>
     <data>
       <neighbor>10.5.14.2</neighbor>
       <interface>fe-1/3/0.0</interface>
     </data>
     <message>RSVP neighbor 10.5.14.2 up on interface fe-1/3/0.0</message>
   </notification>

Yes, I hear you gag on the obnoxious verbosity compared with the
traditional syslog line:

Oct 18 16:01:37  farmer-john rpd[2958]: RPD_RSVP_NBRUP: RSVP neighbor 10.5.14.2 up on interface fe-1/3/0.0


XML-ification of syslog contents is what I meant in my last message.
IMO, what you describe here is not re-inventing syslog but rather
mapping syslog string message format to NETCONF XML format in a
predictable way. (I hope that's what you meant :-)


Thanks,
Phil



Andy



--
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/>