hanfsi
Just log directly to json, it makes any processing later so much easier.
I have and had plenty of full days of coding smart solutions where, when i was in the flow, would even forget that i hit 8h work.
If i really hit my head against a wall because i literaly have an issue i can't figure out right now, i will still try to find different angles or take a walk but i will not just close my laptop after 2-4h of work oO?!
Why? Because you are not building a tracer but a monitoring tool.
Your dashboard is very hard to read because it is basically just tables and your tables do not give you any visual cue. I would highly recommend getting some icons from something like https://fontawesome.com/ and make it visual clear in what screen you are.
If you have any status text, like open/closed etc. give them appropriate color like green and red.
With your rules, it does look like code so why not with a coding theme? Like how githubs markdown makes code different from the rest of the text.
Give buttons appropriate colors.
with your live view, make sure that certain text is aligned vertically;
Give your Memory graphs proper units. 500000000 is not helpful.
I would highly recommend you to take a little bit of time to look to current existing and well working solutions so you can see what makes sense and what doesn't.
I would argue that not using something like Grafana for your frontend, is a big missing feature.
The dashboard gives you a very bad overview. Its not even clear with one look what you are looking at.
And then as a kicker, not a timeseries based database.
You should have a look at how prometheus is doing it.