Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
I use the logger a lot to keep track of what happens in my system. But there are a few things that I really don't need. Would it be possible to make it optional to show the names of the macros that run and the name of the actions that run inside a macro? An example:
I am looking for some way to reduce log verbosity. I am using EG for home automation and my log gets flooded with various events from sensors just because I have one macro that writes sensors value to a database.
One solution could be to temporarily disable the event. But if I do so, I would no longer get the values written into my database.
It would be nice that next release of EG allows enabling/disabling log of specific sets of events/macros/commands. I see 2 possibilities:
1) a system of log "layers" where we could assign events/macros/commands to named layers of log and then activate any of these layers to be actually displayed. New items would be assigned to Default layer that would correspond to current log
2) an option to enable/disable log of any folder (and the events/macros/commands it contain)
I hope 1) or 2) or both could be implemented in a near future
Check out this, it should be covering most since you can basically block all events from being logged (but still working as events). This is however configured differently to what you drafted