Docker container monitoring support?

[DeLuks2006]

Hi, love the UI on this and was wondering if I could somehow use this tool to monitor my docker-services like on uptime-kuma? If not, are there any plans to add support for that later on?

[ajhollid]

Hi @DeLuks2006,

If the services running in your docker containers expose a health endpoint then you can set up a monitor pointing to that endpoint.

Are you looking at monitoring the containers themselves or the services they are running?

[DeLuks2006]

Currently I'm unable to check since I am not at home, but if I remember correctly it takes the container ID and monitors via a socket or via the http(IP:port) of the containers.

[ajhollid]

OK thanks for the info, I'll have a bit of a dig and see if it's something we can add in a reasonable amount of time 👍

If you recall, did you have to expose your docker daemon in order to monitor containers?

[DeLuks2006]

Yup, I had to expose it in order to monitor the containers.

[ajhollid]

I figured as much.

Seems like this should be a fairly straightforward feature to implement. Most of the work would be on the users end exposing their daemon and setting up certificates if they want to use tls.

I'll add it to our issues backlog and we'll work on it. Thanks for your input and help here!

[gorkem-bwl]

Do you need anything on my end @ajhollid for this?

[ajhollid]

@gorkem-bwl if you wouldn't mind putting a figma design together for this flow that would be really great!

It would be an additional type for our the Uptime type montioring, along with ping and http.

It would need an additional field to state whether to use TCP or socket, like the http / https switch we have right now.

[ajhollid]

@DeLuks2006 I've opened up a PR with a basic implementation of docker container monitoring.

Currently it only supports connection via unix socket, we may include http/https connection as well if this is requested.

Is there any particular information you are looking for from a docker container? Or is it sufficient to know the container is in the running state?

I imagine the container state is the most pertinent information:

"State": {
    "Status": "running",
    "Running": true,
    "Paused": false,
    "Restarting": false,
    "OOMKilled": false,
    "Dead": false,
    "Pid": 9937,
    "ExitCode": 0,
    "Error": "",
    "StartedAt": "2024-11-13T02:11:24.020863886Z",
    "FinishedAt": "0001-01-01T00:00:00Z"
},

Let me know if there' anything else you'd like and we can look at incorporating that.

[DeLuks2006]

Hi there, yeah It's just important to know if the containers are in the running state. I usually use the feature over http but It's no big deal, I can just switch over to unix sockets. Anyways awesome work and thank you very much for implementing the feature! :D

[ajhollid]

@DeLuks2006 no problem, thanks for the request, it's great to know what features folks are looking for! The feature is merged in and I've pushed new docker images. If you are running via docker compose you'll have to mount your docker daemon socket to the server image:

    volumes:
     - /var/run/docker.sock:/var/run/docker.sock:ro

When using uptime kuma were you connecting to the docker daemon via http without TLS? Or via https? It's not a big deal for us to add secure and insecure http connection options, just wondering what the typical use case is.

Is there any official documentation for setting up Uptime Kuma for Docker container monitoring? I was just over there taking a look at their docs and I didn't see anything official regarding Docker container monitoring, though it clearly supports it.

I'm trying to figure out what level of documentation/instruction to include for end users.

Thanks again for your help with this feature!

[DeLuks2006]

Hey there, yeah I just used it without TLS but as far as I know it also supported TLS. The whole setup for the docker container monitoring was not documented if I remember correctly; so I had to experiment and rely on other sources such as youtube for example. However it was pretty easy to set up once I got the hang of it, if you want I can share the steps I had to take for the setup once I get home. :)

[ajhollid]

Hey there, yeah I just used it without TLS but as far as I know it also supported TLS. The whole setup for the docker container monitoring was not documented if I remember correctly; so I had to experiment and rely on other sources such as youtube for example. However it was pretty easy to set up once I got the hang of it, if you want I can share the steps I had to take for the setup once I get home. :)

Thanks for the info, yeah the docker daemon does support tls connection and uptime kuma appears to work with it too.

I imagine you'd have to have to point the app to the ssl certs as well as the signing authority if the certs are self signed. This would only be useful if you were making a remote connections to a docker daemon somewhere other than localhost. Not much point in encrypting traffic between me, myself, and I sitting here at the same machine 😂 For local use unencrypted should be sufficient

Sure if you still recall the steps you had to take please do share them. I think I've got a good handle on how it must work, but it's always good to have confirmation.

Thank you!

[NathanAP]

Hey guys, quick question:

In my server I have two projects, each one has their own Docker compose, but of course they do not repeat ports.

Is it possible to have Checkmate in a third Docker to monitor the two others?

[ajhollid]

Hi @NathanAP,

Yes this is definitely possible, you need to expose your Docker daemon to Checkmate, but you will be able to monitor your docker images after doing so.