this post was submitted on 15 Dec 2025
103 points (99.0% liked)

Selfhosted

53705 readers
720 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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!

you are viewing a single comment's thread
view the rest of the comments
[–] Sunspear@piefed.social 3 points 1 day ago* (last edited 1 day ago)

So many upvotes without a comment :/ Sadly I don't have much useful info to add either, I'm looking forward to how others do it as well, since I recently noticed this panel in Beszel too.

Honestly, I use the status icons in Homepage dashboard as a health check, since I always use my dashboard to navigate to apps. Red status indicator -> I have to go fix it. Nothing more severe.

But for point 3 I do have a strong hunch that it depends on the container image creator - a health check is usually just a command that either succeeds or not (or a http response that gets a 200 or not), so it can be as simple as pointing a request to the root url of the app. Of course, this is not the most performant way to check this, which is why app makers may also put in explicit liveness/readiness or similar endpoints that return a really short json to indicate their status. But for the containers that have a healthcheck, they must be implemented in the image (too) I think