- 0 minutes to read

Apache Camel, Logging, FAQ, Binary Data, PDF Attachments, Base64 Encoding Apache Camel, binary data, PDF attachments, images, Base64 encoding, SOAP attachments, email attachments, file transfers, JSON Log Event, insurance claims, document retention, blob storage, Azure Blob, AWS S3 Log binary data (PDF attachments, images) from Apache Camel routes using Base64 encoding. Include in JSON Log Event Body field. Supports large files (tested to 50MB). Alternative: Store large binaries in blob storage, log URL + hash.

Can I log binary data (PDF attachments, images)?

Can I log binary data (PDF attachments, images) from Camel routes?

Yes—Base64 encode and include in Body. Apache Camel routes processing emails with PDF attachments, REST APIs receiving image uploads, or file transfers with binary formats can log the full content.

Example: Camel route receives SOAP request with embedded PDF attachment. Extract attachment bytes, Base64 encode: Base64.getEncoder().encodeToString(pdfBytes). Include in [JSON Log Event][] Body field. Nodinite stores unlimited size (tested to 50MB per event).

Use case: Insurance claims processing—customer submits claim with scanned documents. Compliance requires 7-year retention of original documents. Nodinite logs full PDF/image Base64, searchable by Claim Number. Auditors retrieve original documents 5 years later without separate document storage system.

Performance tip: For very large binaries (>10MB), consider storing in separate blob storage (Azure Blob, AWS S3) and logging the blob URL + hash in Nodinite. Balances searchability (metadata in Nodinite) with cost (large files in cheap blob storage).

See all FAQs: [Troubleshooting Overview][]