Server resource monitoring

MikeAMikeA Hosting ProviderOG
edited July 31 in Services and Other

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.

View of the main dashboard. Mobile friendly, you can add to your home mobile device screen. There's pages to check past alerts, manage your org/acc, manage alerting channels, etc.

Comments

  • 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?

    Backend Ruby Dev and Linux user

  • MikeAMikeA Hosting ProviderOG

    @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.

  • can i use my extravm login details to use srvcheck or do i need new username and password?

  • MikeAMikeA Hosting ProviderOG

    @lapua said:
    can i use my extravm login details to use srvcheck or do i need new username and password?

    no, everything is completely separate.

    --

    I added a few additional things;

    • Swap memory activity so you can see when swapping takes place (since this can hurt server perf, good to know)
    • Disk I/O; see disk IO stats for ever device, read/write use, read/write IOPS, read/write await ms
    • Partition inode usage over time
  • @MikeAPlatinum said: Agent app uses 17~MB memory

    Not bad, I am seeing ~11MB avg, 13.7MB peak on a Storage VPS. After about 24 hours of running it.

    Is there some way to confirm the push frequency if so desired, like once every 2 minutes or 5 minutes? I see the alerting is configurable, but I didn't see the reporting.

    sysmon-agent.service - System Monitor Agent
         Loaded: loaded (/etc/systemd/system/sysmon-agent.service; enabled; preset: enabled)
         Active: active (running) since Thu 2026-07-30 14:18:04 EDT; 1 day 1h ago
       Main PID: 112557 (sysmon-agent)
          Tasks: 6 (limit: 4651)
         Memory: 11.6M (peak: 13.7M, swap: 28K, swap peak: 28K)
            CPU: 15.417s
         CGroup: /system.slice/sysmon-agent.service
                 └─112557 /usr/local/bin/sysmon-agent
    
    Jul 31 15:32:05 sysmon-agent[112557]: 2026/07/31 15:32:05 push ok: HTTP 204
    Jul 31 15:33:05 sysmon-agent[112557]: 2026/07/31 15:33:05 push ok: HTTP 204
    Jul 31 15:34:05 sysmon-agent[112557]: 2026/07/31 15:34:05 push ok: HTTP 204
    Jul 31 15:35:05 sysmon-agent[112557]: 2026/07/31 15:35:05 push ok: HTTP 204
    Jul 31 15:36:05 sysmon-agent[112557]: 2026/07/31 15:36:05 push ok: HTTP 204
    Jul 31 15:37:05 sysmon-agent[112557]: 2026/07/31 15:37:05 push ok: HTTP 204
    Jul 31 15:38:05 sysmon-agent[112557]: 2026/07/31 15:38:05 push ok: HTTP 204
    Jul 31 15:39:05 sysmon-agent[112557]: 2026/07/31 15:39:05 push ok: HTTP 204
    Jul 31 15:40:05 sysmon-agent[112557]: 2026/07/31 15:40:05 push ok: HTTP 204
    Jul 31 15:41:05 sysmon-agent[112557]: 2026/07/31 15:41:05 push ok: HTTP 204
    
  • MikeAMikeA Hosting ProviderOG
    edited July 31

    @stupidgeniusUser said: Is there some way to confirm the push frequency if so desired, like once every 2 minutes or 5 minutes? I see the alerting is configurable, but I didn't see the reporting.

    You can edit the /etc/sysmon-agent/agent.conf on the server:
    INTERVAL=60s
    The default interval is based on the plan settings (60s for these for now), so just change it to 300s for 5 minutes and restart the sysmon-agent service. But really having a lower interval doesn't cause any extra resource use.

    If you're referring to something else let me know.

    Edit - If you're asking about it due to the system log entries for the agent push, I will add a config setting to disable logging the push output.
    Edit 2 - Update agent and add LOG_PUSH=0 and restart to avoid logging now. It's disabled by default now.

  • @MikeAPlatinum said: Edit - If you're asking about it due to the system log entries for the agent push, I will add a config setting to disable logging the push output.

    Yeah, I meant configure, not confirm, sorry. Yes, that should do it.

    Jul 31 16:45:39 sysmon-agent[124028]: 2026/07/31 16:45:39 sysmon-agent 1.7.0 starting: endpoint=https://srvcheck.com interval=5m0s interface="" mounts=all
    

    I was wanting to run this on a few test servers where I don't need 1m monitoring for me every couple minutes is fine.

    Reducing non-error logging (or adding logging levels to the conf) would be nice.

Sign In or Register to comment.