ws-monitoring VS bottom

ws-monitoring

This one is really lightweight and do real time graphs and more: https://github.com/elestio/ws-monitoring/

Shameless plug,I made a lightweight real time monitoring tools using websockets, it's open source: https://github.com/elestio/ws-monitoring/

You will find samples for both in this repo: https://github.com/elestio/ws-monitoring

Here is my half baked real-time server monitoring system: https://github.com/elestio/ws-monitoring

It's a web UI + websocket backend, very small, 10kb vanilla frontend and 300 LOC for the backend.

My goal is not to compete with netdata or other big tools but serve my own needs using really few resources

bottom

I'd suggest Bottom as a TUI alternative to the in-built task managers - https://github.com/ClementTsang/bottom

It works on Windows also.

If anyone is looking for a "top" like, written in Rust, might have a look at https://github.com/ClementTsang/bottom

Looks like bottom with another theme

bottom - A cross-platform graphical process/system monitor with a customizable interface and a multitude of features.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.