Defaults for interval/retry or bulk edit #1764

New issue

Closed

opened 2026-02-28 02:31:50 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 02:31:50 -05:00

Owner

Originally created by @luckman212 on GitHub (Jan 11, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

It would be awesome if:

defaults could be set somewhere so new monitors default to 60-3-20 (for example)
we could select multiple monitors (of same type) and change the parameters en masse

✔️ Solution

After setting up 40 or so ICMP monitors, I started getting false alarms with 1 dropped ping packet. I realized the defaults of 60-0-60 are not ideal for me. I prefer 60-3-20. But now I have to manually edit each monitor and re-save it.

❓ Alternatives

I think I could execute some SQL directly on the db to do the bulk update of these parameters, but I am not sure if that is safe.

📝 Additional Context

No response

Originally created by @luckman212 on GitHub (Jan 11, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description It would be awesome if: - defaults could be set somewhere so new monitors default to 60-3-20 (for example) - we could select multiple monitors (of same type) and change the parameters en masse ### ✔️ Solution After setting up 40 or so ICMP monitors, I started getting false alarms with 1 dropped ping packet. I realized the defaults of 60-0-60 are not ideal for me. I prefer 60-3-20. But now I have to manually edit each monitor and re-save it. ### ❓ Alternatives I think I could execute some SQL directly on the db to do the bulk update of these parameters, but I am not sure if that is safe. ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:31:50 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 02:31:55 -05:00

Author

Owner

@luckman212 commented on GitHub (Jan 12, 2023):

For now, I poked around the SQLite db and figured out how to do it manually.

List all monitors with some detail

# sqlite3 -header /app/data/kuma.db 'select id,type,name,hostname,interval,maxretries,retry_interval from monitor'

Update all ICMP monitors that don't have retries==3 and interval==20:

# sqlite3 /app/data/kuma.db 'UPDATE monitor SET maxretries = 3, retry_interval = 20 WHERE type = "ping" AND (maxretries != 3 OR retry_interval != 20)'

@luckman212 commented on GitHub (Jan 12, 2023): For now, I poked around the SQLite db and figured out how to do it manually. List all monitors with some detail ``` # sqlite3 -header /app/data/kuma.db 'select id,type,name,hostname,interval,maxretries,retry_interval from monitor' ``` Update all ICMP monitors that don't have retries==3 and interval==20: ``` # sqlite3 /app/data/kuma.db 'UPDATE monitor SET maxretries = 3, retry_interval = 20 WHERE type = "ping" AND (maxretries != 3 OR retry_interval != 20)' ```

deekerman commented

2026-02-28 02:31:56 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jul 13, 2023):

@luckman212
I think this is a partial duplicate of https://github.com/louislam/uptime-kuma/issues/455
Duplicates only create immortal zombies and are really hard to issue-manage.
Could you edit your issue (description + title) to make this unique? ^^

@CommanderStorm commented on GitHub (Jul 13, 2023): @luckman212 I think this is a partial duplicate of https://github.com/louislam/uptime-kuma/issues/455 Duplicates only create immortal zombies and are really hard to issue-manage. Could you edit your issue (description + title) to make this unique? ^^

deekerman commented

2026-02-28 02:31:56 -05:00

Author

Owner

@luckman212 commented on GitHub (Jul 14, 2023):

@CommanderStorm You are correct, this appears to be a duplicate of #455. I will close this one, thank you.

@luckman212 commented on GitHub (Jul 14, 2023): @CommanderStorm You are correct, this appears to be a duplicate of #455. I will close this one, thank you.