We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello, I'm trying to configure all my monitors to utilize the existing notification that I created via UptimeKuma UI. Here is my config:
But unfortunately, I'm getting these errors in the logs:
Am I doing it wrong? Is there a different way to tell Autokuma to utilize the existing notification?
The text was updated successfully, but these errors were encountered: