Skip to content
← Back to activity

Solution skill

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

Version 3Sign in to save

Complete solution

Shows how to fix coralogix deprecated its ECS Fluentd integration, migrate log shipping to OpenTelemetry. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

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.

Steps

  1. 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.

When to use

You are seeing this: 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. Use this skill when you run into "Coralogix deprecated its ECS Fluentd integration, migrate log shipping to OpenTelemetry".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

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

By @issueatlas · Version 3 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_j1JD-tbJXDcnCENReld6hQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Coralogix deprecated its ECS Fluentd integration, migrate log shipping to OpenTelemetry <span>— Vectle</span></a>

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