Idea for the log tab

[WernerderChamp]

At the moment, the only way to view hornet logs is by checking the logs via console. While those logs are detailed and good for finding issues, the average user is overwhelmed by it. The log tab should therefore only contain a limited subset of information, allowing a quick check to see if anything notable has happened in the last time

I would split the entries in this tab into 3 categories:

Information: Anything that is worth to show, but does not require user action, e.g. peers connecting, node sync again after falling behind, mana changes to the node in the last x hours, maybe some average mps metrics, ... community probably has some more ideas
Warning: This category is for events that might pose a problem, e.g. only 1-2 healthy peers, node on high load for a longer time, node falling behind/not receiving milestones, processor queue full, milestones taking way too long to solidify, node running low on disk space/memory, etc.
This can probably help a lot when looking into more hidden bugs.
Error: This one is used when something very bad happens, e.g. no sync peers, hornet entering database revalidation, etc.

If the node has not been sync after a restart, most warnings (like no available peers) should be suppressed until the node is sync for the first times

The user can filter by category using icons on the top (select & deselect). By default only warnings and errors show, unless there are none.
Also the time interval can be adjusted via dropdown. The log entries are rotated after 14 days by default.

This could also help with finding long-term errors, without scrolling through days of logs.

[MaKla89]

I'd strongly support this proposal. I'm lacking an easy method to see if and when my node lost sync, for how long and ideally also how many TPS / CTPS were last registered before that loss of sync.

[msarcev]

This needs support from hornet side, to make the zipped logs available through some endpoint.
No priority at the moment for this.