Maybe it’s well known but I just came across journalctl-desktop-notification and I find it very useful so I thought I’d mention it. It’s basically a bash script that monitors systemd’s journal and pops up a notification when there are warnings or errors (or anything else you want to make it catch besides the default config).

What makes it so useful for the selfhoster is that it can monitor the journal on hosts your user has ssh access to with key authentication (set up in 2s with ‘ssh-copy-id’).

So case in point, this just popped up:

My reverse proxy can’t renew certs, that’s bad. For some reason netdata didn’t catch it, and the service didn’t trigger a system email that would have been forwarded to my smtp. Uptime kuma would have caught it when I would have had only a few days to fix it, but this caught it immediately, and I have 52 days to figure it out.

So you install that on your daily driver and you get these notifications on your desktop. They only have packages for Arch and Gentoo but the thing is just a batch script and a systemd unit. So to install anywhere you just download the “source”, extract it, cd to it, and run ‘sudo cp -r usr etc /’ which is exactly what the Arch package does (line 22).

Just a nifty little tool I wanted to share in case others haven’t heard of it.

  • corsicanguppy@lemmy.ca
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    1 hour ago

    Ha ha ha.

    I love how lennart’s cancer tries to replicate fucking syslog and it’s this bad. What a mess the kids worship.

  • Azzu@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    4 hours ago

    Assuming the uptime of your services are in any way important.

    I’m not running a business here, I’ve got no big stakeholders. If something doesn’t work, at most me or someone close to me is affected. No one really cares if something is not available for a day.

    I spent 0 minutes on monitoring and don’t intend to start now :D

    • groet@feddit.org
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 hours ago

      There is still a good reason to know about problems early. Without any monitoring you will find out about problems exactly in that moment when you what to use the service that doesn’t work. Sometimes you need something quick and you don’t have time to debug and fix in that moment. If you get an alert early you can decide to fix it right away or in a few hours or tomorrow.

      • Azzu@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 hour ago

        What do you need quick? I have a Minecraft server, a wiki for random stuff, a shopping list, a calendar sync, photo hosting, a media server and probably some other shit on there.

        I can think of many situations where I’d want those quickly, but need I don’t anything.

        • RheumatoidArthritis@mander.xyz
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 hour ago

          Calendar sync? I learned that Nextcloud went to shit again when I missed an event added by my spouse to the shared calendar. Pretty important to me.

    • FurryMemesAccount@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 hours ago

      Does your data matter ? There’s a data loss prevention risk and security.

      If you don’t care about those either, then I guess your decision makes sense

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    7 hours ago

    This is cool but for self-hosting you probably want a more robust monitoring system capable of alerting at all times. Prometheus is what I use. It also gathers data over time and can monitor many machines.

  • frongt@lemmy.zip
    link
    fedilink
    English
    arrow-up
    21
    ·
    15 hours ago

    If you want the next level up, set up a log collector like graylog or something.

      • non_burglar@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        ·
        13 hours ago

        Hahaha nice. I have PTSD from teaching the interns how to search graylog and then locking up elastic with piped conditional searches.

    • 4am@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      10 hours ago

      Gray lot requires a newer version of mongo. Mongo now requires a processor with the AVX instruction set; and my aging homelab is one gen before Sandy Bridge.

      So basically no graylog for me because I ain’t got money to run that shit anymore let alone upgrade it