Some way to stop all alerts for X period of time? (part of backups) #2442

Closed
opened 2026-02-28 02:54:58 -05:00 by deekerman · 5 comments
Owner

Originally created by @jaxjexjox on GitHub (Aug 8, 2023).

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

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

I would love to 'pause' notifications.

I know about the docker exec command to reset my password, would love something like

docker exec -it <container name> bash
npm run pause 10m

Currently I do the following on my server.

sudo docker stop kuma
sudo docker rm kuma
sudo cp /kumadatafolder/ /backups/kumadatabackup/
sudo docker run (etc etc etc)

In doing this - it will go and spam out a whole heap of emails again, if anything is out of action.
Be nice to stop that, for the duration of the backup process somehow

It might be possible, I'm not aware (apologies)

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

All

💻 Operating System and Arch

22.04 - docker (latest, always)

🌐 Browser

NA

🐋 Docker Version

Docker version 24.0.5, build ced0996

🟩 NodeJS Version

No response

Originally created by @jaxjexjox on GitHub (Aug 8, 2023). ### ⚠️ 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](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem I would love to 'pause' notifications. I know about the docker exec command to reset my password, would love something like ``` docker exec -it <container name> bash npm run pause 10m ``` Currently I do the following on my server. sudo docker stop kuma sudo docker rm kuma sudo cp /kumadatafolder/ /backups/kumadatabackup/ sudo docker run (etc etc etc) In doing this - it will go and spam out a whole heap of emails again, if anything is out of action. Be nice to stop that, for the duration of the backup process somehow It might be possible, I'm not aware (apologies) ### 📝 Error Message(s) or Log _No response_ ### 🐻 Uptime-Kuma Version All ### 💻 Operating System and Arch 22.04 - docker (latest, always) ### 🌐 Browser NA ### 🐋 Docker Version Docker version 24.0.5, build ced0996 ### 🟩 NodeJS Version _No response_
deekerman 2026-02-28 02:54:58 -05:00
  • closed this issue
  • added the
    Stale
    help
    labels
Author
Owner

@CommanderStorm commented on GitHub (Aug 8, 2023):

What you are refering to is the maintance mode:
image

@CommanderStorm commented on GitHub (Aug 8, 2023): What you are refering to is the maintance mode: ![image](https://github.com/louislam/uptime-kuma/assets/26258709/c34849d4-6982-4087-86db-043c93f70d15)
Author
Owner

@jaxjexjox commented on GitHub (Aug 8, 2023):

Can I "inject" maintenance mode into my instance via cli, before stopping my container, and then cancel it again via cli ?

@jaxjexjox commented on GitHub (Aug 8, 2023): Can I "inject" maintenance mode into my instance via cli, before stopping my container, and then cancel it again via cli ?
Author
Owner

@CommanderStorm commented on GitHub (Aug 8, 2023):

You can, but not via first-party tooling, as ahead of time configuration would be against the "project-style" and the API is currently in this state #118

See https://github.com/lucasheld/uptime-kuma-api for further details on the third party I was referring to

@CommanderStorm commented on GitHub (Aug 8, 2023): You can, but not via first-party tooling, as ahead of time configuration would be against the ["project-style"](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#project-styles) and the API is currently in this state #118 See https://github.com/lucasheld/uptime-kuma-api for further details on the third party I was referring to
Author
Owner

@github-actions[bot] commented on GitHub (Nov 6, 2023):

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] commented on GitHub (Nov 6, 2023): 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.
Author
Owner

@github-actions[bot] commented on GitHub (Nov 8, 2023):

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

@github-actions[bot] commented on GitHub (Nov 8, 2023): This issue was closed because it has been stalled for 2 days with no activity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#2442
No description provided.