-  2 minutes to read
                        
                        Apache Camel Logging - FAQ & Troubleshooting
Find quick answers to common questions about logging Apache Camel applications with Nodinite.
Common Questions
| # | Question | Quick Answer | 
|---|---|---|
| 1 | Can business users search without Kusto knowledge? | Yes—Log Views with role-based access enable 2-second searches by Order Number, Customer ID, etc. Zero Kusto knowledge required. | 
| 2 | Can I extract data I forgot to log initially? | Yes—Create Search Field Expression months later, click "Reindex" to extract from all historical payloads. Zero Camel code changes needed. | 
| 3 | Can I use different retention policies per message type? | Yes—Configure per Message Type. Financial transactions kept 7 years (SOX/PCI-DSS), debug logs 30 days, audit trails 10 years. | 
| 4 | Can I log binary data (PDFs, images)? | Yes—Base64 encode and include in Body context property, or store reference URLs to external storage and log metadata only. | 
| 5 | Do I need to change all routes at once? | No—Change routes incrementally. Deploy logging to high-value routes first, then gradually roll out. Gradual adoption recommended. | 
| 6 | How do I correlate transactions across multiple Camel routes? | Use ApplicationInterchangeId in JSON Log Event. Generate GUID at entry point, propagate through all routes via Exchange headers. | 
| 7 | Can I extract exception details from logged data? | Yes—Include exception stacktrace, exception type, and business context in JSON Log Event. Create Search Fields to extract specific exception properties. | 
| 8 | Can Pickup Service handle high-volume routes? | Yes—Handles 100K+ messages per day per route. Asynchronous processing with automatic retry ensures zero data loss. | 
| 9 | How does Nodinite compare to Splunk/ELK cost? | 85% cost reduction. Unlimited retention without per-GB ingestion fees. SQL Server storage (familiar, licensable). Message-Type based retention. | 
| 10 | What happens if Pickup Service goes down? | Intermediate storage (file/HTTP/database/MQ) buffers messages. Pickup Service auto-resumes with retry. Zero data loss during outages. | 
| 11 | Can I use multiple logging frameworks? | Yes—Supports Log4J, SLF4J, Logback. All write to same JSON Log Event format. Mix frameworks across different Camel contexts if needed. | 
| 12 | What intermediate storage options are available? | Local files (high volume/performance), HTTP/HTTPS (real-time), database tables, message queues. Choose based on reliability/volume needs. | 
Need More Help?
- Prerequisites - Review system requirements
- Installation Guide - Step-by-step setup instructions
- Features Documentation - Detailed feature guides