Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020 
<== Date ==> <== Thread ==>

Subject: Re: log message filter in Asyn
From: Eric Norum <wenorum@lbl.gov>
To: <matthew.pearson@diamond.ac.uk>
Cc: tech-talk Talk <tech-talk@aps.anl.gov>
Date: Tue, 17 Apr 2012 08:12:30 -0700
 I'm interested in seeing the discussion arising from your suggestion.  My first reaction is that this sort of log message filtering belongs in the message logger rather than in the ASYN layer. 

On Apr 17, 2012, at 5:05 AM, <matthew.pearson@diamond.ac.uk> wrote:

> 
> Hi,
> 
> Is there any interest in having a log message filter down in the Asyn layer?
> 
> We would like to be able to reduce the amount of Asyn error messages (ASYN_TRACE_ERROR) without having to implement crude filters in the drivers. Asyn error messages are commonly used for comms errors, or other warnings and errors. However, these can be printed to the IOC shell either at the record scan rate or a driver polling rate. So having the ability to reduce these down to, say, once a minute or every 10 minutes, would be useful.
> 
> It could be done using a hash of the message string and building an ordered hash table with a few fields in it (hash, counter, time). To reduce memory impact, and avoid resizing, the table could be kept at a fixed size (say a 100 or 1000 entries), with old entries removed if new ones need to be entered.
> 
> The existing print API would have to be kept the same, and by default rate limiting could be turned off. If it's turned on then it defaults to a certain rate limiting behaviour. But the algorithm could be tweaked at runtime.
> 
> Any thoughts on this? I've kept the above ideas fairly simple and focused on log message rate limiting only. As I guess we don't want anything too complicated done in Asyn that could affect the memory footprint or speed too much.
> 
> I tried to search tech talk in case people have discussed this before, and I couldn't find anything. Although how best to reduce Asyn error message noise has been discussed.
> 
> As an aside to this, how many sites use centralised logging systems?
> 
> Cheers,
> Matthew
> 
> DLS Controls

-- 
Eric Norum
wenorum@lbl.gov



References:
log message filter in Asyn matthew.pearson

Navigate by Date:
Prev: Re: Channel Access problem over SSH Andrew Johnson
Next: RE: log message filter in Asyn Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020 
Navigate by Thread:
Prev: RE: log message filter in Asyn Mark Rivers
Next: How to debug record processing? Nerses Gevorgyan
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·