- 0 minutes to read

Apache Camel, Logging, FAQ, Retention Policies, Compliance, Data Lifecycle Apache Camel, retention policies, Message Types, compliance, SOX, PCI-DSS, 7-year retention, ACH payments, wire transfers, debug logs, audit trails, automatic purge, storage costs, Azure Blob, AWS S3 Configure different retention policies per Apache Camel route type using Message Types. Financial transactions require 7-year retention (SOX/PCI-DSS), debug logs 30 days, audit trails 10 years. Automatic purging reduces storage costs.

Can I keep different retention policies for different route types?

Can I keep different retention policies for different Camel route types?

Yes—configure per Message Type. Financial transactions (ACH payments, wire transfers) require 7-year retention for SOX/PCI-DSS compliance. Debug logs from Camel route testing need only 30 days. Audit trails (user actions, configuration changes) require 10 years.

Configuration: In Nodinite, each [Message Types][] has "Retention Days" setting. "ACH Payment" = 2,555 days (7 years). "Debug Log" = 30 days. "Audit Trail" = 3,650 days (10 years). Nodinite automatically purges old events per-type.

Cost optimization: Shorter retention = lower storage costs. Archive old events to cheap blob storage (Azure Blob, AWS S3) if regulatory requirements mandate longer retention but searchability not required.

See all FAQs: [Troubleshooting Overview][]