Container webhook no UP notification if health-check is used | Wrong Service URL

[SeimusS]

⚠️ Please verify that this bug has NOT been raised before.

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

🛡️ Security Policy

• [X] I agree to have read this project Security Policy

📝 Describe your problem

Hello,

Let me first thank you for this awesome tool. It changed the way how I am deploying monitoring probes (a long time user of blackbox here :)). It solved a lot of troubles I had with blacbox over the years.

Lately I did implement a Webhook notification to Discord server, for everything else that is not a container it work perfectly however for the docker containers I hit some problems:

1. If container has configuration for a health-check it will not trigger a UP notification via the webhook to Discrord

   • For containers that doesnt have a health check UP is recieved normaly, this only seems to affect container with health-check

2. If Kuma sends a notification via webhook to Discord server the Service URL is wrong

   • This is a wierd one for some reason when I recieve the notification on Discord the service URL shows an IP that has nothing to do with the Containers. Meaning on this device is no docker/containerization made.

Can somebody advice?

📝 Error Message(s) or Log

I am monitoring containers via exposed docker.socks, the hearthbeat and retry is set to default 60/1/60

Example of 1. Issue:

Example of 2. Issue is visible from above, I dont understand why it reports that IP as the Service URL

🐻 Uptime-Kuma Version

Version: 1.23.3

💻 Operating System and Arch

Rasbian

🌐 Browser

FireFox 119.0.1 (64-bit)

🐋 Docker Version

Docker 24.0.6

🟩 NodeJS Version

No response

[SeimusS]

In regards of the 2. Issue I fixed this, there was a missconfiguration on my side. The Docker related probes had an IP set. I was cloning a probe that was HTTPs based with this IP and changed it from HTTPs to Container. Looks like when doing this the URL field in HTTPs option remained which caused to report the Event via Webhook with this specific Service URL.

In regards of 1. issue I tried as well other containers set for healthchecks, looks like the issue is related only to "Dashy". Other containers with healtcheck doesnt have this problem. What is wierd for Dashy is that Kuma sees the event starting and then healthy but wont even put the healthy event on the Dashboard. Have the feeling this is a problem of Dashy itself. If anybody has some idea why advices are appreciated :)

Regards, S.

[github-actions[bot]]

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 2 days with no activity.