Hi Gary Yes, it uses the weewx manager. I am afraid that the concepts of classes and subclasses are beyond my comprehension. I have bastardised weewx by editing manager.py to only log a message if database is NOT mesowx, which has at least stopped the log being overrun with 2 second record add entries!! I would prefer a better method though, since obviously I need to remember this edit with any weewx upgrades in the future.
On Sunday, 26 August 2018 06:59:13 UTC+3, gjr80 wrote: > > Andrew, > > Not familiar with mesowx raw service, is it using the Manager class in > manager.py to add records using its addRecord method? If so the addRecord > method supports changing the log level it uses, but it appears that WeeWX > does not give the user the ability to change this log level without editing > the WeeWX code. That being said, in in a vanilla WeeWX install it would be > very easy to subclass StdArchive to make use of this ability to change the > log level. As for mesowx that really depends on how mesowx is > structured/operates, it may be just as simple, it may not. Can you post the > offending log entries, that will give me an idea. Tied up otherwise this > arvo but can have a dig through mesowx later. > > Gary > > On Sunday, 26 August 2018 13:47:17 UTC+10, Andrew Milner wrote: >> >> Is there a way to stop log messages from manager when records are added >> to a database? The mesowx raw service seems to log every loop record added >> to the loop database - and whilst this was never a problem with a FO >> station and a loop record every 53 seconds, it is a huge logging overhead >> with my new VP2 and 2 second loop intervals!!!!!! >> > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
