starred/uptime-kuma

Fork

You've already forked uptime-kuma

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Code Issues 754 Projects Packages Wiki Activity

Enhancements #18

New issue

Open

opened 2026-02-28 01:31:52 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-28 01:31:52 -05:00

Owner

Copy link

Originally created by @Panja0 on GitHub (Jul 12, 2021).

First of all great work! Looks really awesome. Though I have a few enhancement requests to make it even greater! 👍

Select all monitors at once to pause them: at the moment you have to pause them all manually one by one
Scheduled pausing: for scheduled maintenance, server reboot etc (https://github.com/louislam/uptime-kuma/issues/191)
Retries: for instance 3 retries in xx seconds before a service is being marked as down
Accepted HTTP codes: I would like to add status codes to some HTTP request, 401 for instance (#173 )
Public dashboard: create a status page where monitors can be shown but not edited
2FA: would be great to have 2FA (Google auth, Authy etc) for logging in with the admin account
Send notification/alert after xx time: have an interval for sending notifications, to avoid small downtimes
Reset/delete up/downtime history: be able to delete the history for a monitor (after history delete it's 100% up again)
Version number on webinterface (thx @rezzorix)
Link to this github page (thx @rezzorix)
Monitor groups: e.g. Server1, Server2 etc. (thx @LeviSnoot)
Re-order monitors: create your own list priority (thx @LeviSnoot)
Combined monitors : A monitor that looks at two instances but is displayed as one and/or has a dropdown to show all contained (thx @LeviSnoot)
Dark mode: based on system settings (thx @LeviSnoot)
Incident reports: ties into public status page, the ability to write a message relating to the status of a monitor, with a status on each message such as "⛔ Investigating", "⚠ Resolving" and "✔ Resolved". (thx @LeviSnoot) (https://github.com/louislam/uptime-kuma/pull/1253)
White labeling public status page with custom logo, page title and favicon - that said there should obviously still be credit to the project, maybe in the form of a footer or something (thx @LeviSnoot)
Pagination: next page for the Dashboard / Dashboard of each monitor (thx @rezzorix) (https://github.com/louislam/uptime-kuma/issues/4106 https://github.com/louislam/uptime-kuma/issues/2993)
Import/export monitors list as JSON (thx @kvpt)
Add the possibility to define an announcement (thx @kvpt)
Ability to use a separate docker container as the database e.g. mariadb (thx @joe-eklund)
Ability to authenticate with digest or basic auth (thx @joe-eklund)
Heartbeat monitoring, instead of pinging services, those services must check in (thx @joe-eklund)
Able to ignore SSL issues for specific monitors (thx @joe-eklund)
User management with LDAP and oAuth. This would allow us to use our built in user management tools instead of having to create yet another user for people that need access. (thx @joe-eklund) (#128)
Ability to set default notifications in settings so you don't have to select each time you create a new monitor
"Check now" button to perform a check a single monitor right away (thx @parityhero)
Tags to group monitors with filtering: by tag, by type (thx @parityhero)
More information about monitor: date created, last modified etc. (thx @parityhero) (https://github.com/louislam/uptime-kuma/issues/3481)
Ability to SMTP multiple email addresses or CC/BCC (thx @parityhero)
Personnalize notifications for texts / icons to be used, depending on private/public channels for example (thx @magicgg91) (#975)
Check certficate validity and expiration time (thx @magicgg91)
Ability to configure how long the monitor history is retained. A global setting to automatically delete monitor entries older than ${x} days would declutter the user interface. (thx @Spiritreader)
Ability for a "Bulk Upload" via csv etc (thx @EclipseOfficeTech) (https://github.com/louislam/uptime-kuma/issues/4065 https://github.com/louislam/uptime-kuma/issues/2934 https://github.com/louislam/uptime-kuma/issues/1323)

Keep up the good work!

updates

2021-07-15 @ 3.20pm UTC:
Formatting changed to checkboxes per request @louislam

2021-07-15 @ 4.00pm UTC:
Added enhancements requested by @kvpt

2021-07-17 @ 8.00am UTC:
Added enhancements requested by @joe-eklund

2021-07-19 @ 8.02am UTC:
Added enhancements requested by @parityhero

2021-07-21 @ 9.04am UTC:
Added enhancements requested by @magicgg91

2021-07-29 @ 1.40pm UTC:
Added enhancements requested by @Spiritreader & @EclipseOfficeTech

2023-12-01 @ 17.20pm UTC:
Updated the todo list by @CommanderStorm

Originally created by @Panja0 on GitHub (Jul 12, 2021). First of all great work! Looks really awesome. Though I have a few enhancement requests to make it even greater! 👍 - [x] Select all monitors at once to pause them: at the moment you have to pause them all manually one by one - [x] Scheduled pausing: for scheduled maintenance, server reboot etc (https://github.com/louislam/uptime-kuma/issues/191) - [x] Retries: for instance 3 retries in xx seconds before a service is being marked as down - [x] Accepted HTTP codes: I would like to add status codes to some HTTP request, 401 for instance (#173 ) - [x] Public dashboard: create a status page where monitors can be shown but not edited - [x] 2FA: would be great to have 2FA (Google auth, Authy etc) for logging in with the admin account - [x] Send notification/alert after xx time: have an interval for sending notifications, to avoid small downtimes - [x] Reset/delete up/downtime history: be able to delete the history for a monitor (after history delete it's 100% up again) - [x] Version number on webinterface (thx @rezzorix) - [x] Link to this github page (thx @rezzorix) - [x] Monitor groups: e.g. Server1, Server2 etc. (thx @LeviSnoot) - [x] Re-order monitors: create your own list priority (thx @LeviSnoot) - [x] Combined monitors : A monitor that looks at two instances but is displayed as one and/or has a dropdown to show all contained (thx @LeviSnoot) - [x] Dark mode: based on system settings (thx @LeviSnoot) - [ ] Incident reports: ties into public status page, the ability to write a message relating to the status of a monitor, with a status on each message such as "⛔ Investigating", "⚠ Resolving" and "✔ Resolved". (thx @LeviSnoot) (https://github.com/louislam/uptime-kuma/pull/1253) - [x] White labeling public status page with custom logo, page title and favicon - that said there should obviously still be credit to the project, maybe in the form of a footer or something (thx @LeviSnoot) - [ ] Pagination: next page for the Dashboard / Dashboard of each monitor (thx @rezzorix) (https://github.com/louislam/uptime-kuma/issues/4106 https://github.com/louislam/uptime-kuma/issues/2993) - [x] Import/export monitors list as JSON (thx @kvpt) - [x] Add the possibility to define an announcement (thx @kvpt) - [x] Ability to use a separate docker container as the database e.g. mariadb (thx @joe-eklund) - [x] Ability to authenticate with digest or basic auth (thx @joe-eklund) - [x] Heartbeat monitoring, instead of pinging services, those services must check in (thx @joe-eklund) - [x] Able to ignore SSL issues for specific monitors (thx @joe-eklund) - [ ] User management with LDAP and oAuth. This would allow us to use our built in user management tools instead of having to create yet another user for people that need access. (thx @joe-eklund) (#128) - [x] Ability to set default notifications in settings so you don't have to select each time you create a new monitor "Check now" button to perform a check a single monitor right away (thx @parityhero) - [x] Tags to group monitors with filtering: by tag, by type (thx @parityhero) - [ ] More information about monitor: date created, last modified etc. (thx @parityhero) (https://github.com/louislam/uptime-kuma/issues/3481) - [x] Ability to SMTP multiple email addresses or CC/BCC (thx @parityhero) - [ ] Personnalize notifications for texts / icons to be used, depending on private/public channels for example (thx @magicgg91) (#975) - [x] Check certficate validity and expiration time (thx @magicgg91) - [x] Ability to configure how long the monitor history is retained. A global setting to automatically delete monitor entries older than ${x} days would declutter the user interface. (thx @Spiritreader) - [ ] Ability for a "Bulk Upload" via csv etc (thx @EclipseOfficeTech) (https://github.com/louislam/uptime-kuma/issues/4065 https://github.com/louislam/uptime-kuma/issues/2934 https://github.com/louislam/uptime-kuma/issues/1323) Keep up the good work! <details><summary>updates</summary> <p> _2021-07-15 @ 3.20pm UTC:_ Formatting changed to checkboxes per request @louislam _2021-07-15 @ 4.00pm UTC:_ Added enhancements requested by @kvpt _2021-07-17 @ 8.00am UTC:_ Added enhancements requested by @joe-eklund _2021-07-19 @ 8.02am UTC:_ Added enhancements requested by @parityhero _2021-07-21 @ 9.04am UTC:_ Added enhancements requested by @magicgg91 _2021-07-29 @ 1.40pm UTC:_ Added enhancements requested by @Spiritreader & @EclipseOfficeTech _2023-12-01 @ 17.20pm UTC:_ Updated the todo list by @CommanderStorm </p> </details>

deekerman added the

labels

2026-02-28 01:31:52 -05:00

deekerman referenced this issue

2026-02-28 01:50:34 -05:00

Lost every config during update #558

deekerman referenced this issue

2026-02-28 03:45:05 -05:00

get 200 but found 404 #3918

No Branch/Tag specified

master

npm-update

3.0.X

dev-better-auth

copilot/remove-password-complexity-requirements

2.2.X

copilot/sub-pr-6355

1.23.X

api-via-socketio-client

2.1.3

2.1.2

2.1.1

2.1.0

2.1.0-beta.3

2.1.0-beta.2

2.1.0-beta.1

2.1.0-beta.0

2.0.2

2.0.1

1.23.17

2.0.0

2.0.0-beta.4

2.0.0-beta.3

2.0.0-beta.2

2.0.0-beta.2-temp

2.0.0-beta.1

1.23.16

2.0.0-beta.0

1.23.15

1.23.14

1.23.13

1.23.12

1.23.11

1.23.10

1.23.9

1.23.8

1.23.7

1.23.6

1.23.5

1.23.5-beta.0

1.23.4

1.23.3

1.23.2

1.23.1

1.23.0

1.23.0-beta.1

1.23.0-beta.0

1.22.1

1.22.0

1.22.0-beta.0

1.21.3

1.21.2

1.21.2-beta.0

1.21.1

1.21.0

1.21.0-beta.1

1.21.0-beta.0

1.20.2

1.20.1

1.20.0

1.20.0-beta.0

1.19.6

1.19.5

1.19.4

1.19.3

1.19.2

1.19.1

1.19.0

1.19.0-beta.2

1.19.0-beta.1

1.19.0-beta.0

1.18.5

1.18.4

1.18.3

1.18.2

1.18.1

1.18.0

1.18.0-beta.0

1.17.1

1.17.0

1.17.0-beta.1

1.17.0-beta.0

1.16.1

1.16.0

1.16.0-beta.0

1.15.1

1.15.0

1.15.0-beta.1

1.14.1

1.15.0-beta.0

1.14.0

1.14.0-beta.2

1.13.2

1.14.0-beta.1

1.14.0-beta.0

1.13.1

1.13.0

1.13.0-beta.2

1.13.0-beta.1

1.13.0-beta.0

1.12.1

1.12.0

1.11.4

1.11.3

1.11.2

1.11.1

1.11.0

1.10.2

1.10.1

1.10.0

1.9.2

1.9.1

1.9.0

1.8.0

1.7.3

1.7.2

1.7.1

1.7.0

1.6.3

1.6.2

1.6.1

1.6.0

1.5.3

1.5.2

1.5.1

1.5.0

1.3.2

1.3.1

1.3.0

1.2.0

1.1.0

1.0.10

1.0.9

1.0.8

1.0.7

1.0.6

1.0.5

1.0.4

1.0.3

1.0.2

1.0.1

1.0.0

Labels

Clear labels

type:enhance-existing

No labels

type:enhance-existing

type:new

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

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#18

Reference in a new issue

Repository

starred/uptime-kuma

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?

Rows
Columns