Configure history retention for filter. #4394

New issue

Closed

opened 2026-02-28 04:01:02 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 04:01:02 -05:00

Owner

Originally created by @pcsystemd on GitHub (Oct 29, 2025).

⚠️ Please verify that your question has not already been reported

I have searched the existing issues and found no similar reports.

🛡️ Security Policy

I have read and agree to Uptime Kuma's Security Policy.

📝 Describe your problem

Hello,
Currently, we can filter the retention history for a maximum of one week. I would like to keep the history for at least six months.
Is this possible, and if so, how can I configure it?
Thank you for your help.

📝 Error Message(s) or Log

🐻 Uptime-Kuma Version

1.23.16

💻 Operating System and Arch

Debian

🌐 Browser

Chrome

🖥️ Deployment Environment

Runtime Environment:
- Docker: Version 20.10.5 (Build 55c4c88)
- Docker Compose: Version 1.25.0
- Portainer (BE/CE): Version X.X.X (LTS: Yes/No)
- MariaDB: Version X.X.X (LTS: Yes/No)
- Node.js: Version X.X.X (LTS: Yes/No)
- Kubernetes (K3S/K8S): Version X.X.X (LTS: Yes/No, via [method/tool])
Database:
- SQLite: Embedded
- MariaDB: Embedded/External
Database Storage:
- Filesystem:
  - Linux: ext4/XFS/Btrfs/ZFS/F2FS
  - macOS: APFS/ HFS+
  - Windows: NTFS/ReFS
- Storage Medium: HDD/eMMC/SSD/NVMe
Uptime Kuma Setup:
- Number of monitors: X

Originally created by @pcsystemd on GitHub (Oct 29, 2025). ### ⚠️ Please verify that your question has not already been reported - [x] I have searched the [existing issues](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue%20sort%3Acreated-desc%20) and found no similar reports. ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Describe your problem Hello, Currently, we can filter the retention history for a maximum of one week. I would like to keep the history for at least six months. Is this possible, and if so, how can I configure it? Thank you for your help. ### 📝 Error Message(s) or Log ```bash session ``` ### 🐻 Uptime-Kuma Version 1.23.16 ### 💻 Operating System and Arch Debian ### 🌐 Browser Chrome ### 🖥️ Deployment Environment - **Runtime Environment**: - Docker: Version `20.10.5` (Build `55c4c88`) - Docker Compose: Version `1.25.0` - Portainer (BE/CE): Version `X.X.X` (LTS: Yes/No) - MariaDB: Version `X.X.X` (LTS: Yes/No) - Node.js: Version `X.X.X` (LTS: Yes/No) - Kubernetes (K3S/K8S): Version `X.X.X` (LTS: Yes/No, via `[method/tool]`) - **Database**: - SQLite: Embedded - MariaDB: Embedded/External - **Database Storage**: - **Filesystem**: - Linux: ext4/XFS/Btrfs/ZFS/F2FS - macOS: APFS/ HFS+ - Windows: NTFS/ReFS - **Storage Medium**: HDD/eMMC/SSD/NVMe - **Uptime Kuma Setup**: - Number of monitors: `X`

deekerman

2026-02-28 04:01:02 -05:00

closed this issue
added the
help
label

deekerman commented

2026-02-28 04:01:09 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Oct 29, 2025):

Shure, you can change the history retention in the settings under Monitor History

@CommanderStorm commented on GitHub (Oct 29, 2025): Shure, you can change the history retention in the settings under `Monitor History` <img width="1313" height="779" alt="Image" src="https://github.com/user-attachments/assets/8556172b-ebb2-48cd-96d2-8fbd71ab1e34" />

deekerman commented

2026-02-28 04:01:09 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Oct 29, 2025):

Also consider upgrading to v2.
Lots of bugs surrounding retention and performance are fixed

@CommanderStorm commented on GitHub (Oct 29, 2025): Also consider upgrading to v2. Lots of bugs surrounding retention and performance are fixed