Docker swarm services & labels for selector #2017

New issue

Closed

opened 2026-02-28 02:40:22 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 02:40:22 -05:00

Owner

Originally created by @ralphschuler on GitHub (Mar 18, 2023).

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

I checked and didn't find similar feature request

🏷️ Feature Request Type

New Monitor

🔖 Feature description

Additionally to the containers i would like to monitor swarm services.

And then to change the Selector (Container id) to container or service labels.

✔️ Solution

Instead of using the Container ID the check would use labels either attached to a container or a service.

❓ Alternatives

No response

📝 Additional Context

Im honestly not sure what i should add to it.

its "quite simple".

I looked into it and could maybe be able to implement it myself.
the question is how to start so i dont messup everything.

Originally created by @ralphschuler on GitHub (Mar 18, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type New Monitor ### 🔖 Feature description Additionally to the containers i would like to monitor swarm services. And then to change the Selector (Container id) to container or service labels. ### ✔️ Solution Instead of using the Container ID the check would use labels either attached to a container or a service. ### ❓ Alternatives _No response_ ### 📝 Additional Context Im honestly not sure what i should add to it. its "quite simple". I looked into it and could maybe be able to implement it myself. the question is how to start so i dont messup everything.

deekerman

2026-02-28 02:40:22 -05:00

closed this issue
added the
feature-request

A:monitor

type:enhance-existing
labels

deekerman commented

2026-02-28 02:40:26 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 13, 2023):

likely depends on #957
Related https://github.com/louislam/uptime-kuma/issues/882

@CommanderStorm commented on GitHub (Dec 13, 2023): likely depends on #957 Related https://github.com/louislam/uptime-kuma/issues/882

deekerman commented

2026-02-28 02:40:26 -05:00

Author

Owner

@Chirishman commented on GitHub (Jan 26, 2024):

likely depends on #957 Related #882

Not actually dependent on anything else. If you point at a management node's IP it will answer about the service availability for the whole swarm.

See this workaround: https://github.com/louislam/uptime-kuma/issues/3069#issuecomment-1712935178

@Chirishman commented on GitHub (Jan 26, 2024): > likely depends on #957 Related #882 Not actually dependent on anything else. If you point at a management node's IP it will answer about the service availability for the whole swarm. See this workaround: https://github.com/louislam/uptime-kuma/issues/3069#issuecomment-1712935178

deekerman commented

2026-02-28 02:40:26 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Apr 14, 2024):

I think this is better tracked in https://github.com/louislam/uptime-kuma/issues/4233, as docker-compose and docker swarm are likely not as different.
=> merging these issuses via closing this one as a duplicate.

Tip

If you have a look at the dependency linked in https://github.com/louislam/uptime-kuma/issues/957, @BigBoot has shared https://github.com/BigBoot/AutoKuma, which claims to solve this usecase.
We have not tested if it works as advertised, nor audited said software.

@CommanderStorm commented on GitHub (Apr 14, 2024): I think this is better tracked in https://github.com/louislam/uptime-kuma/issues/4233, as docker-compose and docker swarm are likely not as different. => merging these issuses via closing this one as a duplicate. > [!TIP] > If you have a look at the dependency linked in https://github.com/louislam/uptime-kuma/issues/957, `@BigBoot` has shared https://github.com/BigBoot/AutoKuma, which claims to solve this usecase. **We have not tested if it works as advertised, nor audited said software.**