Server resource monitoring

MikeA

Hi guys, I wanted to share a hosted monitoring/alerting service that I was originally working on. It was originally made to replace some of my own stuff like snmp monitoring and another third party service I was using for common resource alerting/historical data monitoring, and I decided to make a prettier and better version of it that anyone can sign up and use. Foremost, the majority of this was built with AI coding (Kimi V3).

No cost, 15 servers/agents for now.

• View 90 days of historical data for CPU, RAM, storage, iowait, CPU temp, network usage (physical NIC), network traffic (totals), mdadm raid monitoring, reboot monitoring
• Setup and receive alerts if a threshold is hit or server appears offline.
• Receive alerts to Email, Pushover, Discord, Slack, Telegram, Twilio (Calling/SMS), or your own webhook.
• Set global thresholds/limits or per-server
• Add multiple people to have access privileges
• Create multiple separate organizations with their own servers
• REST API (basic for now)
• Supports any Linux with systemd, basic Windows server support. Agent app uses 17~MB memory, pushed statistic data over https/443.

https://srvcheck.com

Don't know what I'll do with it long term yet. If you try it out and want to remove it from your server, just go to the web interface and click the delete button, it'll give you a command on how to remove it from your server easily.

jam

Just about two hours ago, I was looking at your website and noticed a link to something called “smokegraph” that I hadn't seen before, and it reminded me of Smokeping, a tool I often use. After looking at the graphs, I started wondering if you were using any open-source tools for that monitoring system that tracks packet loss.

Does this new service perform that kind of monitoring? Or is Smokegraph some kind of internal tool you guys use?

MikeA

@jam said:
Just about two hours ago, I was looking at your website and noticed a link to something called “smokegraph” that I hadn't seen before, and it reminded me of Smokeping, a tool I often use. After looking at the graphs, I started wondering if you were using any open-source tools for that monitoring system that tracks packet loss.

Does this new service perform that kind of monitoring? Or is Smokegraph some kind of internal tool you guys use?

no, I just made that with Claude. I used Smokeping in the past and some other similar software but never liked them, and I wanted a more simple/user-friendly way add probes and to try to see latency issues to some niche networks. Honestly it never was going to be public really but I wanted a easy way for some clients to be able to bring it up easily to check on their end, which is why it's just a link in the footer and nothing else. It also just uses a small Go agent to run tests and report back to the web server script to store in a SQL database. If you want a copy of that PM me and I'll send you a zip after I remove some of my stuff from it.

The SRVCheck stuff doesn't do any latency/packet loss checks, and it's not really made for it since it just reports to a centralized server, and doesn't have remote probes to check systems. The smokeping type script you're talking about has a bunch of probes deployed on my looking glass servers.