Structured app logs #192
Description
Maybe some filter on app logs would be useful on this. Like dns realted things, wireguard realted thing, etc. And subfilters/categories like dns (odoh, fallback, changes/errors, dnscrypt, doh, cache, dns53 etc). Some kind of checkboxes to filter some specific behavior to be able to send specific things to highlight and delimit the problem). I imagine going through a Very Verbose log is not easy.
Previously you suggested using Gemini/AI to check the logs. However hallucinations are too common and those just fill the nonsense with "probable" things. It would be needed some kind of text document in order to "train" AI so they actually understand whats going on and can process and understand without assuming so much nonsense. A train prompt/documentation for ai to actually be truthful and not making up things could be beneficial both for you as developers and for users that try to help like me (or just want to understand the logs).
I get that very verbose logs can be very confidential and long and the 3h period before reverting to error only logs would be the most private respectful approach but maybe if one could select that time and pre-filter the logs based on categories/events users could send some not so delicate information and send more specific logs about a specific problem. This is so complicated I would not know how to filter it all TBH and I'm comfortable sending you my private info to help you fixing bugs.