5. How does Pickup Service handle network failures or Nodinite outages?
Part of the WCF Diagnostics Tracing troubleshooting and FAQ guide.
Nodinite provides built-in fault tolerance for trace file delivery, ensuring zero data loss during network failures or system outages. WCF applications write trace files directly to the local file system or a network share, fully decoupling trace capture from log ingestion.
How Trace File Buffering Works
Pickup Service monitors the WCF trace output folder continuously at 10-second intervals by default. When the Log API becomes unreachable due to a network failure, maintenance window, or database upgrade, Pickup Service buffers trace files in the folder for 1–7 days (configurable with disk space limits). No events are lost during an outage.
When the Log API becomes available again, Pickup Service automatically resumes consumption starting from the oldest files first (FIFO queue). This ordering ensures correct event sequencing and complete data recovery after any outage.
Monitoring Unconsumed Files
Use File Monitoring Agent to track unconsumed file count and folder size proactively. Configure an alert when the folder size exceeds 5 GB — this signals that either Pickup Service is not running or a network failure is preventing log ingestion, and requires immediate investigation.
Next Steps
- WCF Diagnostics Tracing - Overview of all features and getting started guides
- Troubleshooting Overview - See all troubleshooting topics and FAQs
Related Topics
- Troubleshooting Overview - See all troubleshooting topics and FAQs
- WCF Diagnostics Tracing - Back to feature overview
- Pickup Service - Pickup Log Events Service overview
- File Monitoring Agent - Monitor folder sizes and file counts