What happens if Nodinite Log API is unavailable—do logs get lost?
Depends on AsyncAppender configuration. Without AsyncAppender (synchronous logging): If Nodinite Log API unavailable (network outage, Nodinite server down), Log4Net Appender throws exception, logs ERROR to local file appender (if configured as fallback), application continues running (logging failure doesn't crash app). Log entries NOT sent to Nodinite during outage are lost unless logged to local file. With AsyncAppender (recommended): Logs queued in memory buffer (500 entries default), AsyncAppender retries sending to Nodinite (3 retries with exponential backoff, 1 sec → 2 sec → 4 sec delays), if still failing after retries, drops oldest logs from buffer to prevent memory exhaustion, logs warning "Nodinite Log API unavailable, dropping logs" to local file appender. Best practice: Configure BOTH Nodinite appender AND local RollingFileAppender as fallback—if Nodinite unavailable, logs written to local file, ops team uses Nodinite Pickup Service to import log files after Nodinite restored (asynchronous logging pattern, zero data loss).
Related Questions
See all FAQs: [Troubleshooting Overview][]