DaysToKeepMonitorEvents - System Parameter
DaysToKeepMonitorEvents sets how many days Nodinite keeps Monitoring Events, the history of state changes on your Resources. The Monitoring Service reads it when it purges old Monitoring Events from the Log Databases.
At a Glance
| Property | Value |
|---|---|
| Key | DaysToKeepMonitorEvents |
| Data type | integer (days) |
| Default | 90 |
| Read by | Monitoring Service |
| Takes effect | At the next hourly Monitoring Service cleanup. No restart needed. |
| Status | ✅ Active |
| Since | Nodinite 4 |
How It Works
Every time a Resource changes its evaluated state (for example, from OK to Error), Nodinite writes a Monitoring Event to the active Log Database. These events are the state change history behind:
- The history in Monitor Views for users whose Role has the View History permission.
- The Resource State History view.
- Custom Reports that count faults or calculate availability.
This retention applies to all Monitoring Events. Once an hour, the Monitoring Service deletes Monitoring Events older than DaysToKeepMonitorEvents days. Purged events are gone from the Resource State History and from Monitor View history.
Choosing a Value
- Keep at least the default
90days in production, so you can compare incidents across a quarter. - Raise the value when your reports or audits need a longer state change history; the Log Databases grow accordingly.
- Lower it in large environments with many Resources that change state often, if Log Database size matters more than history.
Frequently Asked Questions
Can I get purged Monitoring Events back?
No. Once the Monitoring Service has purged them, they are gone. Raise the value before you need the longer history.