[c-nsp] ID Debugs before sending to SYSLOG

Tom ww10ww10 at yahoo.com
Mon Jun 7 15:17:33 EDT 2010


Thanks for your responses. What i'm trying to do is tag flows of the
debugs not each message...When non-debug messages are generated they
contains a facility name, which is easy to filter or search by, but
debugs don't contain any. The whole thing is keep a log of debug ISDN
events to keep them stored for future troubleshooting of incoming
calls. Do you know of any rate-limiting on the messages to prevent a
future DoS, would that work?

thanks


On Jun 7, 1:27 pm, B <deadheadbl... at gmail.com> wrote:
> Tom,
>
> You can add the command "service sequence-numbers" to your config. Don't
> know if that is what you are looking for. Gives each message a unique ID.
>
>
>
> On Mon, Jun 7, 2010 at 12:13 PM, Tom <ww10w... at yahoo.com> wrote:
> > Hello,
> > I was wondering if anyone has a neat way to mark debugs generated by
> > routers before they are send to a syslog server? The issue is that
> > debugs don't contain a facility or anything like that could ID them.
> > When looking over syslog messages it's impossible to filter them out.
>
> >  I think there is a way that I could do this with EEM and tcl but just
> > wanted to make sure that anyone doesn't have any other better ideas on
> > how to filter debugs on a syslog server.
>
> > Thanks in advance.
> > _______________________________________________
> > cisco-nsp mailing list  cisco-... at puck.nether.net
> >https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive athttp://puck.nether.net/pipermail/cisco-nsp/
>
> _______________________________________________
> cisco-nsp mailing list  cisco-... at puck.nether.nethttps://puck.nether.net/mailman/listinfo/cisco-nsp
> archive athttp://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list