Enhancements

[Panja0]

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 (Scheduled monitoring pause #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 (Feat: Implement Max.Redirects & Accepted Status Codes #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) (Timeline-based incident system #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) (Pagination on status pages #4106 Dashboard Display on vertical 4K screen #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) (Allow basic User management without permissions #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) (Admin (portal user) Audit Logs and Activities #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) (Customisation Notification - is it possible (perhaps in a future version)? #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) (Allow bulk upload monitors using a CSV file or JSON file. #4065 BulkActions #2934 Config templates #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

[rezzorix]

Adding some more simple enhancements to this list above:

• version number on webinterface
• link to this github page

[Panja0]

Added them to my post! Thanks @rezzorix

[Panja0]

Added a few more myself as well. :-)

[LeviSnoot]

Great list! Here's some thoughts of my own:

• Monitor groups (e.g. Server1, Server2 etc.)
• Reorder monitors
• Combined monitors (A monitor that looks at two instances but is displayed as one and/or has a dropdown to show all contained)
• Dark mode (based on system setting would be great)

EDIT:

Adding more here as I think of them, cause I'd rather not spam the thread every time I think of something:

• 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").
• 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)

[Panja0]

Thanks @LeviSnoot
Added your enhancements to my post to have a complete list.

[rezzorix]

Would be good if other users add to this thread here more, instead of opening a new one for every single idea they have :)

One addition:

• "Pause all" or "Pause Groups" could be helpful.

Sometimes I have a service update running interrupting service to several or all services... that results in a lot notifications :D

[Panja0]

@rezzorix
Indeed would be handy to post here I guess.

Your addition is already in:
Select all monitors at once to pause them: at the moment you have to pause them all manually one by one

[rezzorix]

Very important and easy to implement:

• Pagination

Pagination (next page) for the Dashboard / Dashboard of each monitor.
Also maybe for the monitor list on the left.
Just auto separate after every 10, 20, xx pages.

I have setup 10 monitors for different services. Some go off for a bit and on again.
Because of that the dashboard is currently already quite long ... and gets longer and longer ... :)

[Panja0]

@rezzorix added to the list!

[kvpt]

Two more suggestions:

Import/export monitors list as JSON

Scenario

• Add and test monitor in local docker
• Export JSON from local
• Import JSON in production

---

Add the possibility to define an announcement

To announce a specific event, like a maintenance or an hardware failure
The announcement is visible in the dashboard header, we can opt-in if a notification is sent or not

[Panja0]

@kvpt added them to the list!

[joe-eklund]

Here are some additional enhancement's I would like to see (in addition to the ones above):

1. Ability to use a separate docker container as the database (e.g. mariadb).
2. Ability to authenticate with digest or basic auth.
3. Heartbeat monitoring (instead of pinging services, those services must check in).
4. Able to ignore SSL issues for specific monitors.
5. 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.

Some additional thoughts on SSL: for anyone who has to deal with custom certs like I do, you can inject your own CA or ignore all SSL cert issues for all monitors by doing the following (note this is a docker stack file for docker swarm, but docker-compose is close):

version: "3.8"
services:
  uptime_kuma:
    image: louislam/uptime-kuma
    volumes:
       - /uptime_kuma/data:/app/data
       - /uptime_kuma/certs:/certs
    deploy:
      restart_policy:
        condition: any
    ports:
      - 3001:3001
    environment:
      - NODE_EXTRA_CA_CERTS=/certs/ca-bundle.crt # inject your CA.
      #-NODE_TLS_REJECT_UNAUTHORIZED=0 # ignore ssl issues, potentially dangerous but useful for testing :)

This is looking like a great start to a project in a space that I think is sorely lacking in up to date tools. I am currently using statping but the fact that it hasn't been updated in months makes me think it's abondanware. Once some of the enhancements listed on this page are implemented I will look at deploying Uptime Kuma to production. 😃

[Panja0]

Added your enhancements to the list @joe-eklund

[program-the-brain-not-the-heartbeat]

Here are some ideas I thought of:

1. Ability to set default notifications in settings so you don't have to select each time you create a new monitor
2. "Check now" button to perform a check a single monitor right away
3. Tags to group monitors with filtering (by tag, by type)
4. Sorting monitors in dashboard
5. More information about monitor (date created, last modified etc.)
6. Ability to SMTP multiple email addresses or CC/BCC

[Panja0]

@parityhero
Added your enhancements to the list. Removed 1 duplicate:
4. Sorting monitors in dashboard --> Re-order monitors: create your own list priority

[magicgg91]

• Dark mode (based on system setting would be great)
  I would also suggest to have a swhitch button between light/dark mode

Few other small suggestions :

• Personnalize notifications for texts / icons to be used (depending on private/public channels for example)
• Check specific status code (200, 400, 500...)
• Check certficate validity and expiration time
• Define treshold for response timewith alert if it's up to defined level in 1 time or average one.

[Panja0]

@magicgg91
Added yours to the list as well. Removed the duplicates.

[Spiritreader]

I have another potential improvement:

The 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.
This would also go in tandem with the "delete all logs for a specific monitor".

It's more control handed over to the user and should only need a toggle and textbox in the global app settings and a database query to prune old entries according to the timestamp.

[DRM-Scripts]

Would love the ability for a "Bulk Upload" via csv etc....

[Dubz]

To expand on monitor ordering, perhaps introduce grouping? Users could sort by group or a main/pair of tags? Additionally, add severity levels for importance and what should be at the top (for both monitors and groups accordingly).

For instance, perhaps have networking components at the top (after all, if they're having issues, a lot of other items could be after that). Then perhaps servers, and finally dwindle down further as each person sees fit. Mostly spitballing here but you get this gist of it.

[rihards-simanovics]

Hey everyone 😊, not sure if this has been mentioned at some point, had a brief scan of the discussion, but I think it would be great if we had an ability to add multiple incidents (incidents history), on individual status pages.

Currently you can only show one and then override it.

Perhaps similar to what IONOS has here: IONOS Service Status

EDIT:

Also just thought of something else, in the emails that get sent out by the monitor I think it would be a good idea to state for how long the monitor has been down.

Say first email says, "the Foo monitor went down", and the next email states when it went up "The Foo monitor is up, it's been down for xx:xx s/m/h".

This is important as sometimes my client websites would go down and since their mail server is on the same server they wont receive the downtime alert but they would receive an uptime alert and wont know for how long their service was down. I know that it's probably not a good idea to host both website and email servers on the same server but some of my larger clients want to have a dedicated server but not spread the eggs across different baskets so to speak.

[kokofixcomputers]

Great Idea! Something to improve on the list: For the select you can add a bit more options like delete also putting a check box to select before the monitor name will also be great to not select all.

[CommanderStorm]

@Panja0

Here are a few links to other PRs/issues:

Select all monitors at once to pause them: at the moment you have to pause them all manually one by one

Will be resolved by #1886 in the 1.23 release

Monitor groups: e.g. Server1, Server2

Resolved since the 1.22 release includes monitor-groups

Re-order monitors: create your own list priority

Will be resolved by #3312 in the 1.23 release

Combined monitors : A monitor that looks at two instances but is displayed as one and/or has a dropdown

Resolved since the 1.22 release includes monitor-groups

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 "no_entry Investigating", "warning Resolving" and "heavy_check_mark Resolved".

Please link #1253

Ability to use a separate docker container as the database

Will be resolved by #2720 in the 2.0 release

Ability to authenticate with digest or basic auth

Basic auth is a thing => Please remove this from the comment

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

Add links to #128 as the trackig issue and #3328, #553, #1575 as duplicates)

More information about monitor: date created, last modified etc

Please add a link to #3481

Personnalize notifications for texts / icons to be used, depending on private/public channels for example

Please add a link to #975 as the tracking issue

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.

Resolved as setting retention is configurable

[CommanderStorm]

I have updated the description of this issue and I am closing it, as this is better tracked in the linked issues.

Maintaining this issue is not something that we are capable of, given the duplications between this issue and other issues