You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to be able to parse my logs and group multiple log lines together.
For example, when I have an exception in Python, it generates several dozen lines, which completely clutters the logs.
I would like to group all these logs together with a button to expand the logs. This would allow displaying only one line for the exception and, if needed, revealing the full exception details.
Since it's not possible to cover all log grouping use cases, a custom log parser is essential.
Describe how you would like to see this feature implemented
No response
Describe any alternatives you've considered
No response
The text was updated successfully, but these errors were encountered:
Dozzle already does grouping of logs. It doesn't support collapsing though.
Adding custom log parsers and customizations is really hard work. It's beyond the time I have to support it. Also Dozzle is written in Go, which is a compiled language. I prefer to create solutions that work for most, such as a grouping that is currently done. If you want to send a PR to improve it then I am happy to accept it. But I wouldn't want to add customizations and custom logics as that over complicates things.
Describe the feature you would like to see
I want to be able to parse my logs and group multiple log lines together.
For example, when I have an exception in Python, it generates several dozen lines, which completely clutters the logs.
I would like to group all these logs together with a button to expand the logs. This would allow displaying only one line for the exception and, if needed, revealing the full exception details.
Since it's not possible to cover all log grouping use cases, a custom log parser is essential.
Describe how you would like to see this feature implemented
No response
Describe any alternatives you've considered
No response
The text was updated successfully, but these errors were encountered: