Automatically add `docker` containers to be tracked

[Acyone]

⚠️ Please verify that this feature request has NOT been suggested before.

• [X] I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

You should add a possibility for Kuma to check what docker containers are running, and start tracking them . This way it would not be needed to manually add them.

✔️ Solution

In my use case, I would want to see appear my running docker containers in the kuma webUI.

❓ Alternatives

I have considered having to add a special label to each container to be tracked (in the docker-compose file)

📝 Additional Context

Netdata has a similar feature : (source)

Netdata auto-detects running containers and auto-populates the right-hand menu with their IDs or container names, based on the configuration of your system.

Flame also has a similar functionnality using labels : (source)

In order to use the Docker integration, each container must have the following labels

[deefdragon]

Just going to reference #882, as this is similar, but for local containers instead of k8s.

[brhahlen]

This would be great, would add a lot more flexibility and less setup in the tool itself, but automatically monitoring when adding a new service via Docker-Compose. That would also add the ability to add the URL as well.

[brhahlen]

Just to illustrate how this would help me: I'm currently in the process of updating all my monitors again, but it looks like I'm going to need(/want) 3 monitors per service:

1. Docker
2. HTTP Internal
3. HTTP External

Image

Right now, I need to add all these manually, which is a painful process. If I could add, for instance:

labels:
 - uptime.monitor.name=Adminer
 - uptime.monitor.Adminer.type=docker
 - uptime.monitor.Adminer.dockerhost=myhost
 - uptime.monitor.name=Adminer-Internal
 - uptime.monitor.Adminer-Internal.type=http
 - uptime.monitor.Adminer-Internal.url=http://adminer

A bit like how Traefik goes about with labels, if that makes sense?

[tenekev]

I'm doing the same thing and such a feature + this notation would be perfect. Utilizing labels would be a killer feature for extensive setups like mine.

I need 3 or even 4 monitors per container which becomes hard to manage very fast.

[raulvasquez]

This would be a great feature to implement.

[paulchartres]

Would love to see that feature!

[CommanderStorm]

@paulchartres @raulvasquez Please refrain from posting +1 / requests for updates things on issues, as this makes issue-management harder. Issues are for discussing what needs to be done how by whom. We use 👍🏻 on issues to prioritise work.

[jbates58]

I just wanted to follow up on this as its been a while, and it seems that it still may not be possible to have containers auto populate kuma. Is this on the roadmap for implementation at all?

Cheers

[CommanderStorm]

Is this on the roadmap for implementation at all?

Currently, this is not on the roadmap for the v2.0-release. You can check what is planned for the milestones here: https://github.com/louislam/uptime-kuma/milestones

v2.0 will include plenty of new features. Most notably the ability to scale past ~300-600 monitors, the ability to run with another database, subdirectory deployments and security enhancements like a rootless docker image.

If you/somebody else would like to implement this feature, here is our contribution guide: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

[CommanderStorm]

docker-compose based group creation will continue to be tracked in #4233 to make this more focused and hopefully more implementable

[BigBoot]

If anyone is interested I've create a small service which creates Monitors based on docker labels: https://github.com/BigBoot/AutoKuma/tree/master