So recently been spending time configuring my selfhosted services with notifications usint ntfy. I’ve added ntfy to report status on containers and my system using Beszel. However, only 12 out of my 44 containers seem to have healthcheck “enabled” or built in as a feature. So im now wondering what is considered best practice for monitoring the uptime/health of my containers. I am already using uptimekuma, with the “docker container” option for each of my containers i deem necessary to monitor, i do not monitor all 44 of them 😅

So I’m left with these questions;

  1. How do you notify yourself about the status of a container?
  2. Is there a “quick” way to know if a container has healthcheck as a feature.
  3. Does healthcheck feature simply depend on the developer of each app, or the person building the container?
  4. Is it better to simply monitor the http(s) request to each service? (I believe this in my case would make Caddy a single point of failure for this kind of monitor).

Thanks for any input!

    • Sips'@slrpnk.netOPEnglish
      2·
      15 hours ago

      Maybe a transition to a cluster homelab should be the goal of 2026, would be fun.

      • Noxy@pawb.social
        English
        2·
        14 hours ago

        maybe! three raspis and k3s have served me mostly well for years, tho with usb/sata adapters cuz the microsd was getting rather unreliable after awhile

        • Sips'@slrpnk.netOPEnglish
          1·
          13 hours ago

          Nice one that, fortunately i just rebuilt my server with an i5-12400 new fancy case amd slowly transitioning to an all in ssd build! I would probably lean towards a singlenode cluster using Talos.

          • Noxy@pawb.social
            English
            1·
            4 hours ago

            I haven’t heard of Talos before, sounds like it’s not fully open source?

            • Sips'@slrpnk.netOPEnglish
              1·
              7 minutes ago

              Talos is really awesome, its a minimal OS strictly built to run kubernetes. We use it at work and its running in production for a lot of people. Its extremely minimal and can only be used via its own api, talosctl command. Its minimalism makes it great for security and less resource heavy than alternatives.

              Check this out for a quick’ funny taste of why one should consider using Talos >>

              [60sec video from Sidero Labs, creators of Talos] https://www.youtube.com/watch?v=UiJYaU16rYU

              Talos is under MPL 2.0, afaik that is open-source.