Can you recommend a service or container for doing disk analysis and reporting failure conditions? - eviltoast

I recently stood up a new file server using ZFS on linux. I’d like to automate the disk checking in such a way that I can essentially ignore and have a service notify me when SMART or other indications are hitting failure or pre-fail levels.

I’m not looking for a fancy GUI or web UI - a plain old config file would suit me just fine. In my ideal world, it would be a container I could simply spin up with minimal configuration, but I’m willing to give anything a try.

    • ASK_ME_ABOUT_LOOM@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      I used scrutiny years ago, but recall not being happy with it for some reason. I’ll give it another try.

      Edit: I remember now. The notification configuration is next-level awful. The documentation is close to nonexistent. Getting basic SMTP auth is non-functional. Finding an actual example of a slack notification configuration is impossible. Have any working configs you can share?

      • Okay6120@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        I used this .yaml example yaml

        I used the pushbutton line and just filled in my details. I use it for a few other apps. There’s a command line test notification on the main GitHub page. It took a couple tries but works when I test.

        The GUI is ok.

        • ASK_ME_ABOUT_LOOM@sh.itjust.worksOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          After a bunch of digging, I was able to find this documentation for configuring Slack integrations with shoutrrr, which is the notification system bolted on to scrutiny. After quite a bit more trial and error, I wasn’t able to get token auth working (it appears shoutrrr’s updated docs are already out of date), but I was able to make webhooks work. Gotta say, shoutrrr’s configuration strings are awfully user-hostile.

          After some more trial and error, I was able to get SMTP auth working after removing all special characters from my password and setting it to a stupidly long randomly generated string.