All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
After Domain Monitor: thinking about a simple server resource monitor – suggestions?
Hey everyone!
After working on our open-source Domain Monitor project, I started thinking about building another small tool and I’d really appreciate some input from the community here before going too far with it. 
The idea is a lightweight server resource monitor with a Go agent. The general concept right now is:
- A small Go agent running on the server
- Collecting metrics like CPU, RAM, disk usage, load, and network
- Sending the data to a central service/dashboard
- Focus on very low overhead and simple deployment
The goal isn’t to compete with large monitoring stacks like Prometheus, Zabbix, or Grafana ecosystems, but rather to create something very simple open source and lightweight for small VPS setups.
Before building too much, I wanted to ask:
- What metrics would you consider essential?
- Would you prefer push agents or pull-based monitoring?
- Any features that are missing from existing lightweight tools?
- What would make you actually use something like this?
We will run one public instance like we did domain-monitor for anyone that is lazy to setup their own. 
Our Domain Monitor project that we previously shared here is now on a stable release with several working features, although we are still continuing development, fixing bugs, and implementing suggestions from the community.
If you didn’t see that thread, you can take a look here:
https://lowendtalk.com/discussion/comment/4747666
https://github.com/Hosteroid/domain-monitor
https://community-scripts.github.io/ProxmoxVE/scripts?id=domain-monitor
Would love to hear your thoughts and suggestions.
Thanks!
Comments
I believe ltstats from @lukast__ already offers something like this.
https://lowendtalk.com/discussion/207783/ltstats-lightweight-open-source-resource-monitoring-system
But cool concept for sure:)
Make sure it works on any UNIX, not just on linux.
Keep the agent really small and light weight (and preferably the server as well).
Not a single line of ai crap!
i'm recently enjoying beszel, not sure how similar that is to what you're considering. seems like this is a quite busy space but i'm a fan of options so looking forward to your developments.
The issue is monitoring market is pretty saturated but if you go ahead, please make it easy deploment and update with docker coz domain monitor never worked in docker for me. Otherwise, cpu steal is important, traffic consumption, especially if I can select date ranges, so I do not have to log into the panel to check how much traffic left. How much storage left. Maybe biggest files on the disk to understand quickly what is eating up space
would recommend to just add it as a "feature" in the existing domain monitor project.
Maybe something more indepth like domain-monitor 😁
Feel free to report me in private message what problems do you have with docker deployment on domain-monitor? Actually cool idea about biggest files and traffic left options! 😇
As an disable/enable feature?
I do not exactly remember what the issue was but it is probably because I use it behind a sophisticated reverse proxy. It works fine without docker, it is just much more comfortable to deploy/update using docker.
Yes, especially traffic because I really need it and the only reliable way to check is to use the panel...but if you have many servers, it is a pain.
At this moment any llm had solid grasp on essential feature list of monitoring scripts. Begin from that and add custom pov.
just vibe coded something similar. took me 4 hours with free credits from gemini
could be enabled by default. Don't care about configurability. Your project could pivot to an "all things monitoring" kind rather than limited to domains. I agree that the agent could be written in golang for portability.