this post was submitted on 15 Dec 2025
110 points (99.1% liked)

Selfhosted

60693 readers
335 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 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
[โ€“] Sunny@slrpnk.net 1 points 7 months ago (1 children)

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.

[โ€“] noxypaws@pawb.social 1 points 7 months ago (1 children)

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

[โ€“] Sunny@slrpnk.net 2 points 7 months ago* (last edited 7 months 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.