starred/uptime-kuma

Fork 0

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

Export skips status pages #2446

New issue

Closed

opened 2026-02-28 02:55:06 -05:00 by deekerman · 4 comments

deekerman commented

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

Owner

Originally created by @barefooter22 on GitHub (Aug 8, 2023).

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

I checked and didn't find similar feature request

🏷️ Feature Request Type

API

🔖 Feature description

It looks like the export feature exports all monitors and alerts, but skips dashboards. I just migrated my instance and while the monitors and the alerts migrated nicely, I had to remake my dashboards which wasn't the end of the world, but would be nice to include in the backup

✔️ Solution

Ideally, the dashboards would be exported in the JSON backup along with everything else.

❓ Alternatives

I was able to rebuild my dashboards without too much effort, but this would make the backup itself more complete in my mind in terms of preserving configuration.

📝 Additional Context

No response

Originally created by @barefooter22 on GitHub (Aug 8, 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 API ### 🔖 Feature description It looks like the export feature exports all monitors and alerts, but skips dashboards. I just migrated my instance and while the monitors and the alerts migrated nicely, I had to remake my dashboards which wasn't the end of the world, but would be nice to include in the backup ### ✔️ Solution Ideally, the dashboards would be exported in the JSON backup along with everything else. ### ❓ Alternatives I was able to rebuild my dashboards without too much effort, but this would make the backup itself more complete in my mind in terms of preserving configuration. ### 📝 Additional Context _No response_

deekerman

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

closed this issue
added the
feature-request

A:settings
labels

deekerman commented

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

Author

Owner

@UptimeKumaBot commented on GitHub (Aug 8, 2023):

Hi, I'm a bot. I'm here to help you to find similar issues: #1500 #555 #2426

@UptimeKumaBot commented on GitHub (Aug 8, 2023): Hi, I'm a bot. I'm here to help you to find similar issues: #1500 #555 #2426

deekerman commented

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

Author

Owner

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

I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/1500
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

@CommanderStorm commented on GitHub (Aug 8, 2023): I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/1500 If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage? If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

deekerman commented

2026-02-28 02:55:13 -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:55:13 -05:00

Author

Owner

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

Chiming in with a more in-depth explainaition:

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 explainaition: 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