DaysToKeepErrorEventsWithoutData - System Parameter
The DaysToKeepErrorEventsWithoutData System Parameter sets how many days the Logging Service keeps error events that have no message data, and therefore no Message Type to take a retention value from. Older ones are deleted on the next cleanup run.
At a Glance
| Property | Value |
|---|---|
| Key | DaysToKeepErrorEventsWithoutData |
| Data type | integer (days) |
| Default | 10 |
| Read by | Logging Service |
| Takes effect | Next cleanup run; no restart needed |
| Status | ✅ Active |
How It Works
Retention for normal Log Events is set per Message Type. Some error events never get one, because they carry no message data. Typical examples are errors raised before a message was received or processed, such as a failed connection or a rejected request. Without this parameter those error events would never expire.
On each cleanup run (see CleanUpTimerInterval), the Logging Service deletes error events without data that are older than this value. Until then, they are visible in Log Views like any other event. The full retention pipeline is described in the Logging Service Data Retention section.
Choosing a Value
- The default
10days gives time to notice and troubleshoot recent system-level errors without letting them pile up. - Raise the value if you need these error events for longer, for example to investigate recurring connection problems.
Frequently Asked Questions
How does this differ from DaysToKeepMessageEventsDefault?
DaysToKeepMessageEventsDefault seeds the retention of events that have a Message Type; after that, each Message Type's own Days to keep Events value applies. DaysToKeepErrorEventsWithoutData applies only to error events without message data or Message Type, so you can keep them for a different, usually shorter, period.