You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I deployed AutoKuma to my Docker Swarm and it wasn't creating any monitors in Uptime Kuma. It wouldn't even add a test static monitor I had configured. After enabling trace logging, I was able to see that it was logging into Uptime Kuma successfully, but wasn't doing anything else. There are no errors in the log file.
After troubleshooting this for some time, I eventually tried removing the AUTOKUMA__DOCKER__SOURCE variable, and it started adding monitors via the container labels. Manually setting AUTOKUMA__DOCKER__SOURCE to Services or Both seems to break AutoKuma.
I also tried deploying it on a standalone Docker host. Setting AUTOKUMA__DOCKER__SOURCE to Services or Both causes similar behavior. Removing the variable, or setting it to 'Containers', allows AutoKuma to work correctly.
Note: This was done against a fresh install of Uptime Kuma v1 (initial testing with v2 showed similar results)
It appears that AutoKuma fails at some point when trying to read the Service labels for some unknown reason. At which point it won't add any monitors, whether configured via static files or container labels.
Could you please add some additional logging to help with troubleshooting issues like this? AutoKuma doesn't seem to log anything about what it was trying to do, what labels it is interpreting, whether it can connect to the Docker sockets, whether the snippet I put in there was understood (I eventually just removed it), etc. The only logs I ever saw were about its connection to Uptime Kuma which, while useful, weren't helpful during the hours of troubleshooting.
Please let me know if you need more info or would like me to test something, I would be happy to help!
The text was updated successfully, but these errors were encountered:
I deployed AutoKuma to my Docker Swarm and it wasn't creating any monitors in Uptime Kuma. It wouldn't even add a test static monitor I had configured. After enabling trace logging, I was able to see that it was logging into Uptime Kuma successfully, but wasn't doing anything else. There are no errors in the log file.
After troubleshooting this for some time, I eventually tried removing the
AUTOKUMA__DOCKER__SOURCE
variable, and it started adding monitors via the container labels. Manually settingAUTOKUMA__DOCKER__SOURCE
toServices
orBoth
seems to break AutoKuma.I also tried deploying it on a standalone Docker host. Setting
AUTOKUMA__DOCKER__SOURCE
toServices
orBoth
causes similar behavior. Removing the variable, or setting it to 'Containers', allows AutoKuma to work correctly.Note: This was done against a fresh install of Uptime Kuma v1 (initial testing with v2 showed similar results)
Stack YAML:
Autokuma docker log:
The configured
autokuma.toml
file is empty.Docker version:
It appears that AutoKuma fails at some point when trying to read the Service labels for some unknown reason. At which point it won't add any monitors, whether configured via static files or container labels.
Could you please add some additional logging to help with troubleshooting issues like this? AutoKuma doesn't seem to log anything about what it was trying to do, what labels it is interpreting, whether it can connect to the Docker sockets, whether the snippet I put in there was understood (I eventually just removed it), etc. The only logs I ever saw were about its connection to Uptime Kuma which, while useful, weren't helpful during the hours of troubleshooting.
Please let me know if you need more info or would like me to test something, I would be happy to help!
The text was updated successfully, but these errors were encountered: