starred/uptime-kuma

Fork 0

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

Add the status page to the backup.json file #987

New issue

Closed

opened 2026-02-28 02:06:19 -05:00 by deekerman · 8 comments

deekerman commented

2026-02-28 02:06:19 -05:00

Owner

Originally created by @Urban-Hacker on GitHub (Apr 15, 2022).

⚠️ 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

I had to restore recently my uptime kuma instance on a brand new installation. I though the .json backup was enough and yes it contains all the monitors but miss the status page which is a bit sad since it forces to manually recreate it.

✔️ Solution

Simply add dashboard info to the json to allow for quick restore

❓ Alternatives

Currently the main alternative is either a low level backup (backing up the database etc) or rebuilding the status page manually.

📝 Additional Context

No response

Originally created by @Urban-Hacker on GitHub (Apr 15, 2022). ### ⚠️ 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 I had to restore recently my uptime kuma instance on a brand new installation. I though the .json backup was enough and yes it contains all the monitors but miss the status page which is a bit sad since it forces to manually recreate it. ### ✔️ Solution Simply add dashboard info to the json to allow for quick restore ### ❓ Alternatives Currently the main alternative is either a low level backup (backing up the database etc) or rebuilding the status page manually. ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:06:19 -05:00

closed this issue
added the
feature-request

A:settings

A:core
labels

deekerman commented

2026-02-28 02:06:22 -05:00

Author

Owner

@tarun7singh commented on GitHub (Apr 20, 2022):

If this issue is still up for grabs I would like to start work on it.
I might need a little bit of guidance on it.

@tarun7singh commented on GitHub (Apr 20, 2022): If this issue is still up for grabs I would like to start work on it. I might need a little bit of guidance on it.

deekerman commented

2026-02-28 02:06:22 -05:00

Author

Owner

@Computroniks commented on GitHub (Apr 21, 2022):

@tarun7singh I don't see any pull requests for this and no one else has said that they are working on it so you might as well take a crack at it. I would recommend creating an empty commit using git commit -m "[empty commit] pull request for <YOUR TASK NAME>" --allow-empty before you start working as this will allow you to create a PR and get some assistance and feedback on your work.

@Computroniks commented on GitHub (Apr 21, 2022): @tarun7singh I don't see any pull requests for this and no one else has said that they are working on it so you might as well take a crack at it. I would recommend creating an empty commit using `git commit -m "[empty commit] pull request for <YOUR TASK NAME>" --allow-empty` before you start working as this will allow you to create a PR and get some assistance and feedback on your work.

deekerman commented

2026-02-28 02:06:22 -05:00

Author

Owner

@prof79 commented on GitHub (May 17, 2022):

This would be very much appreciated (y) Also had a corruption issue yesterday and re-creating a page with 140+ monitors is no fun. Especially, which would be stuff for other feature requests, since you can't sort or mass-move or mass-select stuff, adding monitors only honors the top-most group, ...

@prof79 commented on GitHub (May 17, 2022): This would be very much appreciated (y) Also had a corruption issue yesterday and re-creating a page with 140+ monitors is no fun. Especially, which would be stuff for other feature requests, since you can't sort or mass-move or mass-select stuff, adding monitors only honors the top-most group, ...

deekerman commented

2026-02-28 02:06:22 -05:00

Author

Owner

@kristiandg commented on GitHub (Jul 17, 2022):

I vote for this one as well. A lot of design effort going into laying out the perfect status page, only to lose it would be a huge bummer. :)

@kristiandg commented on GitHub (Jul 17, 2022): I vote for this one as well. A lot of design effort going into laying out the perfect status page, only to lose it would be a huge bummer. :)

deekerman commented

2026-02-28 02:06:22 -05:00

Author

Owner

@Drallas commented on GitHub (Aug 15, 2023):

Is this still open?

@Drallas commented on GitHub (Aug 15, 2023): Is this still open?

deekerman commented

2026-02-28 02:06:22 -05:00

Author

Owner

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

Is this still open?

Yes, this is still an open issue. If you look at the json output of the status pages.

Contributions to https://github.com/louislam/uptime-kuma/pull/2667 are likely welcome.
Currently, the PR is not blocked on functionality/implementation but on testing
⇒ if somebody wants to help @chakflying, this would be appreciated

@CommanderStorm commented on GitHub (Aug 15, 2023): > Is this still open? Yes, this is still an open issue. If you look at the json output of the status pages. Contributions to https://github.com/louislam/uptime-kuma/pull/2667 are likely welcome. Currently, the PR is **not blocked on functionality/implementation but on testing** ⇒ if somebody wants to help @chakflying, this would be appreciated

deekerman commented

2026-02-28 02:06:22 -05:00

Author

Owner

@chakflying commented on GitHub (Nov 21, 2023):

Obsolete as the backup feature has been dropped in #3892.

@chakflying commented on GitHub (Nov 21, 2023): Obsolete as the backup feature has been dropped in #3892.

deekerman commented

2026-02-28 02:06:22 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Feb 8, 2024):

Chiming in with a more in-depth explanation:

Please see https://github.com/louislam/uptime-kuma/issues/2141#issuecomment-1272360952

In 1.18.3, the backup feature was deprecated due to [being left] unmaintained.

Backup & Restore with JSON has been deprecated and issues will not be fixed due to the amount of problems it has been causing for our users and us.
The current design is just not maintainable, causing countless bugs.
In v2.0 the deprecated backup tool is being removed because of this reason.
Please consider using SQL, API based¹ or infrastructure based² backup instead.

New approaches to these features should use SQLite dump or MariaDB dump respectively. (Here is our contribution guide)

You can subscribe to these issues meanwhile:

#2496
#477

using the third-party API: https://uptime-kuma-api.readthedocs.io/en/latest/ ↩︎
see https://github.com/louislam/uptime-kuma/issues/477#issuecomment-1557966187 for a setup example ↩︎

@CommanderStorm commented on GitHub (Feb 8, 2024): Chiming in with a more in-depth explanation: Please see https://github.com/louislam/uptime-kuma/issues/2141#issuecomment-1272360952 > In 1.18.3, the backup feature was deprecated due to [being left] unmaintained. Backup & Restore with JSON has been deprecated and issues will not be fixed due to the amount of problems it has been causing for our users and us. The current design is just not maintainable, causing countless bugs. In `v2.0` the deprecated backup tool is being removed because of this reason. Please consider using SQL, API based[^1] or infrastructure based[^2] backup instead. New approaches to these features should use [SQLite dump](https://www.sqlitetutorial.net/sqlite-dump/) or [MariaDB dump](https://mariadb.com/kb/en/mariadb-dump/) respectively. (Here is our [contribution guide](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md)) You can subscribe to these issues meanwhile: - #2496 - #477 [^1]: using the third-party API: https://uptime-kuma-api.readthedocs.io/en/latest/ [^2]: see https://github.com/louislam/uptime-kuma/issues/477#issuecomment-1557966187 for a setup example