Running services, network usage, memory usage, bandwidth, disk I/O, successful logins, whether the thing is even alive, etc…
So far my only method has been “hope and pray”.

  • owenfromcanada@lemmy.caEnglish
    35·
    15 days ago

    I have a robust monitoring system for my Jellyfin server, been running for the last few years. Checks in periodically, at least once per 24 hours and notifies me if it’s down. Doesn’t use any electricity, but does consume a good amount of Cheerios and mac & cheese.

      • communism@lemmy.mlEnglish
        5·
        14 days ago

        I self-host my own email, have done so for years. I’ve not gotten pwned. Use an SSH key and a firewall, only expose the ports that should be public, have reasonable access controls, etc, just practise general cybersecurity—it applies to servers too.

        I know everyone complains about hosting email. But I’ve not run into major problems. My emails get through spam filters and I have good uptime. It’s also a fun learning experience.

      • bertlewirth@lemmy.worldEnglish
        3·
        14 days ago

        Well, it’s a good learning experience. But…… don’t. Good luck getting around the major email providers’ smart screen shit. It’s probably not gonna happen. I tried a few years ago, and even microslop couldn’t figure out why their shit screen crap wouldn’t allow my emails. It’s not in their best interest to fix it. So they don’t. But it’s worth doing it in the short term to learn how to do it. Teaches you about email, spf, dkim etc. which actually does translate to real world skills. I used what I learnt setting it up in my real life job.

        • Dultas@lemmy.worldEnglish
          3·
          15 days ago

          Yeah, email is one of the more annoying things to self host. Google rejects mine because my ISP has all their non static IPs on block lists (even though my IP hasn’t changed once since I’ve been with them it’s still not “static”, can’t change the reverse DNS) and I’m not paying 150% more a month for a business account to get a static IP. I ended up just using a free email relay. Still had to setup SPF, DKIM, DMARC, and all that jazz still.

          • bertlewirth@lemmy.worldEnglish
            1·
            14 days ago

            Yup. It’s so damn annoying hosting email. Do it once to learn, but don’t do it as a permanent solution. It takes so much maintenance to keep it going, if you even do get it working.

            • InFerNo@lemmy.mlEnglish
              1·
              14 days ago

              What maintenance do you mean? run OS updates and pay the vps bill. that’s true for any self hosted application. which specific maintenance are you referring to?

  • pHr34kY@lemmy.worldEnglish
    5·
    15 days ago

    It’s running the private DNS for my phone. If it goes down, I realise quite quickly.

  • Joelk111@lemmy.worldEnglish
    4·
    14 days ago

    They’re in my attached garage. In the living room when it’s quiet I can hear them humming. Does that count?

  • CameronDev@programming.devEnglish
    3·
    15 days ago

    Uptime Kuma, only really care if it’s up or not. Got about 30 services monitored, sending notifications to Signal.

  • phanto@lemmy.caEnglish
    2·
    15 days ago

    I sync my podcasts hourly with Nextcloud and poddersync, so when my servers go down, my phone beeps at me.

  • corsicanguppy@lemmy.caEnglish
    2·
    14 days ago

    SNMP.

    The old engine was nagios. The new engine will be telegraf -> mqtt -> brokerfest -> timescale -> Prometheus.

    I guess. Not sure yet. The brokerfest is a series of broker pubsub between sites to both split out data from the stream for off-site CC, or pull its own subscriptions in. Data could go host <- telegraf -> broker -> remote broker -> remote timescale -> remote Prometheus

  • Dultas@lemmy.worldEnglish
    2·
    15 days ago

    Uptime Kuma for outages, Prometheus for metrics, rsyslog to Loki backend for logs. Grafana for ingesting Prometheus and Loki data.