Include Status Pages on export #3506

New issue

Closed

opened 2026-02-28 03:31:55 -05:00 by deekerman · 1 comment

deekerman commented

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

Owner

Originally created by @c-michail on GitHub (Jul 30, 2024).

Haven't found related topic

🏷️ Feature Request Type

Settings

🔖 Feature description

Hello,
Please add an option to Include Status Pages on export/import.

Thank you

✔️ Solution

Include Status Pages data into the export json or create new format.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @c-michail on GitHub (Jul 30, 2024). ### 📑 I have found these related issues/pull requests Haven't found related topic ### 🏷️ Feature Request Type Settings ### 🔖 Feature description Hello, Please add an option to Include Status Pages on export/import. Thank you ### ✔️ Solution Include Status Pages data into the export json or create new format. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

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

closed this issue
added the
feature-request

A:settings

duplicate
labels

deekerman commented

2026-02-28 03:31:59 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Aug 2, 2024):

Closing as a duplicate/resolved.
In-depth answer:

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 (Aug 2, 2024): Closing as a duplicate/resolved. In-depth answer: 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