- 0 minutes to read

Apache Camel, Logging, FAQ, Intermediate Storage, File Storage, Pickup Service Apache Camel, intermediate storage, file-based logging, JSON Log Event, Pickup Service, database table, JDBC, message queue, JMS, ActiveMQ, Log API, Docker, Kubernetes, reliability, automatic retry, zero dependencies Choose intermediate storage for Apache Camel logging. File-based recommended: write JSON Log Event files locally, Pickup Service polls and uploads. Alternative: database (JDBC), message queue (JMS), direct HTTP. File storage offers maximum reliability.

Which intermediate storage should I use for Apache Camel logging?

Which intermediate storage should I use for Apache Camel logging?

File-based is recommended for maximum reliability and simplicity. Have your Camel routes write [JSON Log Event][] files to a local folder (/var/log/nodinite/*.json). The [Pickup Service][] polls every 30-60 seconds, uploads successfully, then deletes local files. Benefits: Zero external dependencies (no database, no message queue), automatic retry on network failures, no blocking of Camel routes, works in any environment (Docker, Kubernetes, bare metal).

Alternative: Database table (JDBC INSERT) if you already have database infrastructure. Message queue (JMS/ActiveMQ) if you need guaranteed delivery across network failures. Direct HTTP to [Log API][] (not recommended—synchronous, blocks Camel routes if Nodinite unavailable).

See all FAQs: [Troubleshooting Overview][]