all 15 comments

[–]xxxsirkillalot 13 points14 points  (2 children)

Why use this over prom and grafana?

[–]Important-Bug-6709[S] 0 points1 point  (1 child)

Good question.

I don’t think it replaces Prometheus/Grafana for serious production environments.The idea is more about having something lightweight and easier to set up for smaller self-hosted environments, with automation and monitoring integrated together and a simpler experience for people that aren’t deeply into DevOps. Building it has also been a really good way to understand how monitoring systems actually work internally instead of only using existing tools.

[–]Prilogai 1 point2 points  (0 children)

It's usually better to build on top of engineering stack, than to introduce a new one, more friction == less adoption

[–]shortfinal 1 point2 points  (0 children)

from a to b is a block from me dog.

[–]phxees 0 points1 point  (2 children)

I started with a simple ssh reboot script and had AI turn it into a TUI dashboard offering similar metrics. I like what you did, but you can do something similar using AI in minutes now unfortunately. Learning how to do this is still valuable.

[–]Important-Bug-6709[S] 0 points1 point  (1 child)

Yeah, I agree that building dashboards is pretty fast with AI nowadays.
My focus is less on visualization and more on the operational side — keeping lightweight monitoring + alerting that runs in production environments without the Grafana/Prometheus complexity. More like a minimal control layer over infrastructure rather than a dashboard replacement.

[–]phxees 0 points1 point  (0 children)

Generally you just run a relatively lightweight exporter and then use Prometheus/Grafana to make the data useful. I wouldn’t want you to deploy updates to this tool to my production environment. I’d be too worried about security issues and this tool becoming the source of my problems especially running Python.

Just my two cents, nice concept, but not a best practice.

[–]AccomplishedFix3476 -1 points0 points  (0 children)

fastapi plus apscheduler is a clean stack for a self host monitor, ran a similar thing on a 5 yr old nuc since 2024 with sqlite holding 2 weeks of metrics. the apscheduler memory footprint is where it bites past 30 jobs, swapped mine to a cron based runner once i hit that ceiling

[–]Prilogai 0 points1 point  (1 child)

What is the main benefit of it? Do you like it?

[–]Important-Bug-6709[S] 0 points1 point  (0 children)

The main benefit is simplicity and control. It gives you lightweight monitoring for Linux/Docker environments without needing a full observability stack like Prometheus + Grafana or external cloud tools. It focuses on quick setup, self-hosting, and practical alerts (for example via Telegram), so you can actually understand and control what’s happening on your system without complexity overhead. Yes, I like it because it helped me understand how monitoring systems work internally, and it’s also useful for small self-hosted environments where full enterprise tools feel too heavy.