[asterisk-dev] CLI filtering

[Tzafrir Cohen]

On Thu, Jan 18, 2007 at 06:27:13PM -0800, John Todd wrote:

> I would be very much in favor of "tagging" from a dialplan-accessible 
> (and AMI-accessible) trigger, which could either tag things in the 
> debug log or raise a call to the console output.  I have very busy 
> systems with only particular calls that create problems, and it would 
> be nice to only see the output from the calls that I tag in a certain 
> way, or redirect the output from those specific calls to a custom 
> debug log.
> 
> exten => 1234,1,Debug(track-me,debug,tricky-problem)
> exten => 1234,n,Dial(SIP/blah)
> exten => 1234,n,Debug(track-me,none)
> 
> then, in logger.conf, a line like this:
> 
> track-me => adhoc
> 
> where "adhoc" is a special logging level that takes it's level 
> dynamically from the dialplan/AMI.

Your terminology is a bit incorrect here:
Creating a separate logging facility in the lines of "console" is
probably not a good idea: "console" is a target for logs. What you want
to create is a custom filter for logs. Tht is a custom log level.

That said, I still consider this a reinvention of the wheel. What should
actually be done is proper formatting of the messages so they could it
would be easier to filter them later with grep, awk, and co.

-- 
               Tzafrir Cohen       
icq#16849755                    jabber:tzafrir at jabber.org
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com       
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir