Coralogix deprecated its ECS Fluentd integration, migrate log shipping to OpenTelemetry

If you still run the Fluentd-based Coralogix integration on ECS, plan the migration to the OpenTelemetry collector integration now, do not wait for the legacy endpoints to go dark. Migrate Fargate deployments to the OTel ECS Fargate integration and EC2 deployments to the OTel EC2 path, then verify logs arrive in the Coralogix UI before decommissioning the Fluentd sidecar.

Context: Coralogix telemetry-shippers documents that the AWS ECS Fluentd log integration is deprecated. The legacy endpoints will stop working, so deployments still on the Fluentd integration need to migrate ECS Fargate or ECS EC2 log shipping to the matching OpenTelemetry collector integration before the cutoff, or log flow silently breaks.

Matched source

Source: Published skill Original query: "Coralogix deprecated its ECS Fluentd integration, migrate log shipping to OpenTelemetry" Key terms: coralogix, deprecated, fluentd, integration, migrate, opentelemetry, shipping

Source: Coralogix telemetry-shippers documents that the AWS ECS Fluentd log integration is deprecated. The legacy endpoints will stop working, so deployments still on the Fluentd integration need to migrate ECS Fargate or ECS EC2 log shipping to the matching OpenTelemetry collector integration before the cutoff, or log flow silently breaks.

Verified resolution: If you still run the Fluentd-based Coralogix integration on ECS, plan the migration to the OpenTelemetry collector integration now, do not wait for the legacy endpoints to go dark. Migrate Fargate deployments to the OTel ECS Fargate integration and EC2 deployments to the OTel EC2 path, then verify logs arrive in the Coralogix UI before decommissioning the Fluentd sidecar.

Source URL: https://github.com/coralogix/telemetry-shippers/blob/HEAD/logs/fluentd/aws-ecs/readme.md