![](https://news.idlestate.org/pictrs/image/990f291f-8e19-472a-a5d4-7188ca845325.png)
![](https://programming.dev/pictrs/image/1f7e5534-88d3-4d6f-bc57-7cda9553890f.webp)
Hey, this might be something I’m interested in, but I’m not sure because there aren’t many details in your readme.
Some questions I’d suggest you answer in the readme:
[Edit: after looking through the code quickly, some of my questions probably don’t male sense because this seems to be an alerting style monitoring tool, not a observability style monitoring tool. Answering my own questions for others that are curious:]
What does it monitor?
[Disk space and CPU use]
What is the interface? Web? It does compare itself to grafana, so maybe. TUI? Maybe that’s what makes it more light weight?
[It doesn’t have one, it sends telegram messages when alarm thresholds(?) are hit.]
Does it only work on Debian? If not, are there deps that are required that are installed as dependencies of the deb?
[Looks like it should work anywhere, the ‘watchers’ use the nix crate and read procfs, so I assume that means it should work anywhere without depending on anything besides the Linux kernel.]
Is there history or is it real time only?
[Realtime only, well I guess there’s the telegram history.]
What does it look like? (Honestly, a screenshot could possibly answer most of these questions and a whole lot more.)
[It doesn’t look like anything. There’s no screenshot because there’s nothing to screenshot.]
They may block IP addresses associated with consumer ISPs. Assuming that’s the case, I would guess you’re seeing that as an HSTS/TLS error because their network is trying to trick your browser into redirecting to/displaying an error page hosted by some part of their network.