ws-monitoring VS pcopy

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

nopaste/pcopy, that you can selfhost. Just a single binary file.

Heyy I made a thing like that. https://github.com/binwiederhier/pcopy

And another one here:https://github.com/binwiederhier/pcopy (same, see server.go)

I host a version of it on https://nopaste.net

re 1: as fellow gopher has said, `io.CopyN` is your friend, though I have recently implemented a similar thing that may be interesting to you. I implemented a `Peak()` method that will read up to N bytes and return a reader that can be read as if it's the original reader, but you'll be able to get the `PeakedBytes` from it too: https://github.com/binwiederhier/pcopy/blob/master/util/peak.go

Since we're listing alternatives, here's the one I made: https://nopaste.net -- It's open source and available on https://github.com/binwiederhier/pcopy

curl usage is available via: "curl nopaste.net".

I have an issue on github (https://github.com/binwiederhier/pcopy/issues/20) to "modernize" the JS code a little, i.e. use "class"es, modules, strict mode, consts, exports, ...

If you want to see them implemented, see https://github.com/binwiederhier/pcopy/blob/284b6502fa736951b4ace0dfc62152ff707639ae/server.go

Source is here: https://github.com/binwiederhier/pcopy