Skip to main content
Log shipping to an external provider is a data replication and disaster recovery strategy used to keep a copy of server logs in an off-site location, often hosted by a third-party service provider. This approach ensures that critical server logs are safely stored in a separate location, providing an additional layer of protection in case of data loss, server failure, or other emergencies. When logs are shipped to an external provider, all logs will remain accessible through Control Plane, adhering to the current log retention policy. Control Plane offers the ability to ship all Org logs to the following providers:
  1. Amazon S3
  2. CloudWatch
  3. Coralogix
  4. Datadog
  5. Elastic
  6. Fluentd
  7. Logz.io
  8. Loki
  9. Stackdriver
  10. Syslog
  11. OpenTelemetry

​
Shipping to Multiple Providers

An Org can ship its logs to more than one external provider at the same time. Every log entry goes to each configured provider independently, so one destination failing (bad credentials, a full bucket, a network issue) doesn’t block delivery to the others. The primary provider is set at spec.logging. Up to three additional providers can be added as spec.extraLogging, an array of provider entries, for four providers total. Each entry, whether it’s the primary or one of the extras, configures exactly one provider. The same provider type can appear more than once, for example two S3 buckets, but entries must not be identical.
At least one primary provider (spec.logging) must be configured before extraLogging can be used.
YAML
Each provider’s page shows the CLI YAML for spec.logging; add further providers the same way, as additional entries under spec.extraLogging. cpln org patch replaces the whole extraLogging array, so list every additional provider you want to keep each time you patch it.