DaysToKeepErrorEventsWithoutData – System Parameter
Control how long Nodinite retains error events that have no associated message data with the DaysToKeepErrorEventsWithoutData system parameter. This setting helps manage storage for exception events that lack payload or message type context.
What you'll achieve with this parameter:
- Automatically delete old error events without data
- Prevent accumulation of orphaned exception records
- Balance troubleshooting needs with storage efficiency
- Automated cleanup during maintenance cycles
The DaysToKeepErrorEventsWithoutData System Parameter defines the retention period (in days) for error events that have no associated message data and therefore no Message Type or endpoint assignment. These events typically represent system exceptions or errors that occurred before message processing could begin.
| System Parameter Name | Data Type | Values/Example | Comment |
|---|---|---|---|
| DaysToKeepErrorEventsWithoutData | integer | 10 |
Default = 10 days. Events are deleted during cleanup cycles. |
The Logging Service automatically deletes these error events during its maintenance cycle, controlled by the CleanUpTimerInterval parameter. This ensures that exception records don't accumulate indefinitely while still providing a reasonable window for troubleshooting recent issues.
Note
Changes to this parameter are detected automatically by the Logging Service on the next cleanup cycle. You do NOT need to restart the service for the new value to take effect.
Why This Parameter Exists
Not all errors in an integration platform have associated message data. Common scenarios include:
- Connection Failures - Errors connecting to endpoints before message retrieval
- Authentication Errors - Security failures before message processing
- System Exceptions - Internal service errors unrelated to specific messages
- Invalid Requests - Malformed requests rejected before processing
These error events are valuable for immediate troubleshooting but typically have lower long-term value than errors associated with actual business transactions. A shorter retention period (default 10 days) keeps storage requirements manageable while maintaining recent diagnostic information.
Balancing Troubleshooting & Storage
The default 10-day retention period provides:
✅ Sufficient Time for Issue Detection - Most system errors are discovered and resolved within days
✅ Reduced Storage Overhead - Prevents accumulation of low-value error records
✅ Focus on Business Transactions - Prioritizes retention of actual message-related errors
✅ Automated Maintenance - No manual intervention required for cleanup
Tip
If you need longer retention for compliance or extensive troubleshooting, consider increasing this value. However, ensure your cleanup operations can handle the additional workload during maintenance cycles.
Frequently Asked Questions
Find more solutions and answers in the Nodinite System Parameters FAQ, as well as the Troubleshooting user guide.
How do I change the value?
Changing a value for the pre-defined System Parameters is described in the generic 'How do I change the System Parameters' article.
Do I need to restart anything?
No! The Logging Service uses IOptionsMonitor to detect configuration changes dynamically. When you change this value, the service will pick up the new setting on the next cleanup cycle without requiring a restart.
How does this differ from DaysToKeepMessageEventsDefault?
DaysToKeepMessageEventsDefault controls retention for normal message events that have associated Message Types and data. DaysToKeepErrorEventsWithoutData specifically targets error events that lack message data or type associations. This allows for different retention strategies based on event value.
When are these events actually deleted?
The Logging Service deletes error events without data during its maintenance cycle, which runs at the interval specified by CleanUpTimerInterval (default: 1 hour). Events older than the configured number of days are removed during each cycle.
Can I view these error events before they're deleted?
Yes, error events without data are visible in the Web Client Log Views until they're deleted. You can filter and search for these events to troubleshoot system-level issues.
Next Step
Logging Service
CleanUpTimerInterval
DaysToKeepMessageEventsDefault
Administration