Would be great to have logging granularity #1004
Replies: 2 comments
-
You can already disable all categories of logs via DEBUG environment variable. There's really not much framework for warn/error messages in the code. I agree it might be nice, but it's unlikely to happen at this point as I don't really do much more than keep this working at this point and, quite honestly, I get so few bug reports it's not really worth revamping the entire log system. I don't really know what benefit there is to sending all MQTT logs to a central source. Actually, the default used to be to just not log anything except errors, but people kept thinking nothing was working because they only saw some startup messages and nothing else, so I made the default to log all MQTT messages. |
Beta Was this translation helpful? Give feedback.
-
Hm, how? This does not take any effect in my compose file
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Thanks for a great job you do - this project is the best to integrate Ring setups to HA.

One suggestion if I may - would be great to have a settings for logging severity - like DEBUG, INFO, WARNING, ERROR etc.
I ship all logs to Loki via Alloy, so definitely can try to do custom retention, but just having this "knob" to control log severity would be much easier.
Cheers,
Yury,
Beta Was this translation helpful? Give feedback.
All reactions