search

BigBoot / AutoKuma

AutoKuma is a utility that automates the creation of Uptime Kuma monitors based on Docker container labels. With AutoKuma, you can eliminate the need for manual monitor creation in the Uptime Kuma UI.
MIT License
309 stars 15 forks source link

Hooking up existing notification #102

Open lordlightman opened 4 days ago

lordlightman commented 4 days ago

Hello, I'm trying to configure all my monitors to utilize the existing notification that I created via UptimeKuma UI. Here is my config:

AUTOKUMA__DEFAULT_SETTINGS: |-
  *.notificationIDList: { "1": true }

But unfortunately, I'm getting these errors in the logs:

              /\           | |         | |/ /                         
             /  \    _   _ | |_   ___  | ' /  _   _  _ __ ___    __ _ 
            / /\ \  | | | || __| / _ \ |  <  | | | || '_ ` _ \  / _` |
           / ____ \ | |_| || |_ | (_) || . \ | |_| || | | | | || (_| |
          /_/    \_\ \__,_| \__| \___/ |_|\_\ \__,_||_| |_| |_| \__,_|  
                                                                v0.8.0
INFO [autokuma::sync] Updating monitor: openspeedtest_docker
WARN [autokuma::sync] Encountered error during sync: Server responded with an error: insert into `monitor_notification` (`monitor_id`, `notification_id`) values (57, '1') - SQLITE_CONSTRAINT: FOREIGN KEY constraint failed
INFO [autokuma::sync] Updating monitor: openspeedtest_http
WARN [autokuma::sync] Encountered error during sync: Server responded with an error: insert into `monitor_notification` (`monitor_id`, `notification_id`) values (56, '1') - SQLITE_CONSTRAINT: FOREIGN KEY constraint failed

Am I doing it wrong? Is there a different way to tell Autokuma to utilize the existing notification?