[GH-ISSUE #2171] Manage Check History Retention per Check #1347

New issue

Open

opened 2026-03-02 02:22:40 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 02:22:40 +03:00

Owner

Originally created by @adamjrberry on GitHub (Mar 16, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2171

Is your feature request related to a problem? Please describe.
Currently check history appears to be stored per the setting in Global Settings > Retention > Check History. In most cases this is optimal, but in some cases, users may need to define different retention policies for checks. In my case, I'm showing a specific check status on a Grafana dashboard and only need to know about it if it's currently failing, while there are some other checks that it's useful to keep a history of.

Describe the solution you'd like
The ability to set retention policies for Checks on a per-check basis. It would be good to have the ability to disable storing history for specific checks.

Describe alternatives you've considered
Not sure of any alternatives that wouldn't also result in logging. I did consider doing this as a task instead of a check, but it seems tasks can only be ran as quickly as daily on Linux currently, and I'm not sure of the logging/db overhead for this as well.

Additional context
This is less of an issue and more of a 'nice to have'. I'm just mindful that I'm causing entries in my database from checks when the history of this specific check is irrelevant and doesn't need to be stored. I run this check fairly frequently.
In this case, I'm using a check to report when there are available APT Updates, and also another to report on needrestart status. The history of these checks is useless to me, I only need the current data, and if I need any historical data, that is already being piped to our syslog collector.
If anyone has any suggestions on how to achieve this in the meantime, I'd be keen to hear.

Originally created by @adamjrberry on GitHub (Mar 16, 2025). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2171 **Is your feature request related to a problem? Please describe.** Currently check history appears to be stored per the setting in Global Settings > Retention > Check History. In most cases this is optimal, but in some cases, users may need to define different retention policies for checks. In my case, I'm showing a specific check status on a Grafana dashboard and only need to know about it if it's currently failing, while there are some other checks that it's useful to keep a history of. **Describe the solution you'd like** The ability to set retention policies for Checks on a per-check basis. It would be good to have the ability to disable storing history for specific checks. **Describe alternatives you've considered** Not sure of any alternatives that wouldn't also result in logging. I did consider doing this as a task instead of a check, but it seems tasks can only be ran as quickly as daily on Linux currently, and I'm not sure of the logging/db overhead for this as well. **Additional context** This is less of an issue and more of a 'nice to have'. I'm just mindful that I'm causing entries in my database from checks when the history of this specific check is irrelevant and doesn't need to be stored. I run this check fairly frequently. In this case, I'm using a check to report when there are available APT Updates, and also another to report on needrestart status. The history of these checks is useless to me, I only need the current data, and if I need any historical data, that is already being piped to our syslog collector. If anyone has any suggestions on how to achieve this in the meantime, I'd be keen to hear.