Hi guys,
I just released a new version of MinMon. If you’re looking for a minimalistic tool for monitoring and alarming, check out the documentation and give it try! And even more important: please leave some feedback as I’ll have some spare time next month to - hopefully - make v1.0 happen, or at least v0.6.
Cheers!

  • sneakyninjapants@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    1 year ago

    Thanks for sharing! I’ll definitely be looking into adding this to my infra alerting stack. Should pair well with webhooks using ntfy for notifications. Currently just have bash scripts push to uptime-kuma for disk usage monitoring as a dead man trigger, but this should be better as a first-line method. Not to mention all the other functionalities it has baked in.

    Edit: Would also be great if there was an already compiled binary in each release so I can use bare-metal, but the container on ghcr.io is most-likely what I’ll be using anyway. Thanks for not only uploading to docker hub.

  • nbailey@lemmy.ca
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Very cool! I like the idea of a less-weird Monit. I might try this on some one-off servers later…

      • nbailey@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        The config dsl syntax is a bit strange, can’t run a script on “recovery”, but it’s generally not bad honestly. I use it on loads of servers as a monitoring-tool-of-last-resort if the main system fails.

  • TCB13@lemmy.world
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    13
    ·
    1 year ago

    “Simple, clean, bloat-free” – proceeds do use Docker lol.

    • derevar@feddit.de
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      2
      ·
      1 year ago

      In my opinion docker is simple. And only one dependancy is quite bloat-free in my book as well. :)

        • mim@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          5
          ·
          1 year ago

          You can always compile it, it’s just a single cargo command. 🤷‍♂️

        • float@feddit.deOP
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          That’s actually not a bad idea. There are a few downsides to this like the binary being quite big compared to the classical “one binary per architecture” style. I’ll give it a though. The docker image is pretty small btw ;).

          • TCB13@lemmy.world
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 year ago

            You can simply not bundle typical libraries that are available in most systems and let package managers deal with those.

            • float@feddit.deOP
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              I think the dependencies might actually be a problem for the “one binary fits all” solution. For a simple binary the user is responsible for the external dependencies. If by any chance you’re using Arch, there a package in the AUR.