BigBoot

@johntdyer Unfortunately it's not possible to create a one size fits all solution here, because autokuma just doesn't have all the same information as your traefik instance, so you might...

Sorry the documentation here was wrong, the correct property name is `notification_name_list`

Hi, are the any messages in the AutoKuma log? The first thing that comes to mind is that you are using container_name as id, which might include characters that are...

Hmm this is weird, are you sure the jellyseer container actually exists and is on the same docker host as autokuma?

Here are some things I can think of: - Make sure you're using the stable/latest version, not master, at least for testing - if you're using swarm, make sure the...

@UninspiredENVY you can try running autokuma with increased logging by setting the following env variable: `RUST_LOG=kuma_client=trace,autokuma=trace`. Be aware that the generated log might contain sensitive information so I'd advise against...

The error doesn't seem to be related to the posted config. The error is saying that autokuma is unable to parse the arguments in a snippet call (i.e. a label...

Hi there, it looks like there's multiple things going wrong here: First of the value you need to use for the `..._name` providers in generally the "autokuma id", how this...

``` INFO [autokuma::sync] Creating new Monitor: vault-active-monitor INFO [autokuma::sync] Updating Notification: pagerduty-notification INFO [autokuma::sync] Updating Notification: slack-notification INFO [autokuma::sync] Updating Notification: pagerduty-notification INFO [autokuma::sync] Updating Notification: slack-notification INFO [autokuma::sync] Updating...

this should be working in master, please reopen if the issue persists