Feature Request: Grouping Logs by Request URL Within a Single File

[vildanbina]

Hello team,

I've been exploring your log viewer package and really appreciate the work put into it. It's been instrumental in simplifying log analysis for my projects. However, I've encountered a scenario where further categorization of logs could enhance usability and efficiency, especially when dealing with large log files.

Feature Idea:
My proposal is to introduce a feature that automatically groups all logs related to a single request, based on the request URL, within a log file. This would enable users to quickly identify and analyze all log entries associated with specific request URLs, improving the debugging process for applications with numerous endpoints.

Benefits:
Enhanced Debugging Efficiency: By grouping logs by request URL, developers can more quickly identify issues related to specific endpoints.
Improved Log Readability: This categorization could help in decluttering log files, making it easier to navigate through relevant entries.
Streamlined Analysis: For applications that generate extensive logs, this feature could significantly streamline the log analysis process, enabling faster resolution of issues.

I believe this addition could greatly benefit many users of the log viewer package, making it an even more powerful tool for developers. I'd love to hear your thoughts on the feasibility of this feature and any suggestions you might have.

Thank you for considering my proposal. Looking forward to your feedback.

[arukompas]

Hey @vildanbina

Thanks for the request!

Just so I understand correctly, the grouping by requests - requests means requests to your app, where you sometimes log data about that request for debugging purposes, right?

If so, then that in itself is not a usual or defined spec - every developer will give a different context for the log entry with a different structure.

So if we are to introduce some kind of grouping inside Log Viewer, then it probably needs to group by a certain context attribute value, which really could be anything - request url, user ID, queued job name, etc.

At least that's how I imagine a potential solution 😀

I agree this would be a great addition to the Log Viewer, but for now I have very limited time (just had a baby 2 days ago) so I don't plan on working on this big feature any time soon.

Feel free to give it a go yourself and submit a PR! Just bear in mind I'm very picky about UX 😅

Hope this makes sense 🙌

This is a very cool feature idea, though, something I have also thought about before and something I could use at work 😄 especially for grouping exceptions!