aws-otel-collector icon indicating copy to clipboard operation
aws-otel-collector copied to clipboard

ECS FireLens compatibiltiy: Make it a drop in replacement for aws for fluent bit

Open project0 opened this issue 2 years ago • 22 comments

Is your feature request related to a problem? Please describe.

Most applications still send (structured/plain) logs to stdout and then depends on external scraping. Some opentelemetry sdk also do not support full OTLP log forward so there is no real alternative as of today.

Someone already using the opentelemetry collector for traces and metrics may also want to have a better integrated way with logs in ECS (Fargate). As of today there is no official documentation how to setup logging with the otel collector in AWS. Afaik there are only two native ways: awslogs (cloudwatch) or firelens.

I did some research and experimented how to setup otel collector and i am actually surprised it works pretty well, so i wonder why i did not find any resource :sweat_smile: As Firelens is at the end just fluentd forwarding to a sidecar container, i do not see any reasons why we cannot just use the otel collector instead of a additional fluentd sidecar.

Describe the solution you'd like

  • Extend the components with the fluentforward receiver (native protocol support) and transform processor (required to parse json body logs)
  • Provide example configs in docs

Additional context

I put the relevant configs and a example task definition together, maybe someone else wants to use it today, but the ADOT is not supporting the relevant components yet: https://github.com/project0/aws-ecs-firelens-opentelemetry

project0 avatar Nov 03 '23 17:11 project0

@project0 thank you so much for this! Would you be willing to discuss this with me (ADOT PM) in some greater detail? I'm based out of Ireland, so shouldn't be too hard to find some time slot that works for both of us.

mhausenblas avatar Nov 07 '23 13:11 mhausenblas

Also interested in this. @mhausenblas if you haven't already connected with @project0 and it would be helpful to provide any additional thoughts from my end, please let me know.

luxaritas avatar Dec 15 '23 21:12 luxaritas

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

github-actions[bot] avatar Feb 18 '24 20:02 github-actions[bot]

Keep open please!

luxaritas avatar Feb 18 '24 20:02 luxaritas

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

github-actions[bot] avatar Apr 28 '24 20:04 github-actions[bot]

Let's bump this one more time - hoping there has been some movement on it?

jameshulse avatar Apr 28 '24 22:04 jameshulse

Bumping this. This feature would be tremendously helpful!

greaterthanmost avatar Jun 19 '24 17:06 greaterthanmost

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

github-actions[bot] avatar Aug 18 '24 20:08 github-actions[bot]

Bump to keep open

luxaritas avatar Aug 19 '24 00:08 luxaritas

Seems like @hyperdxio adopted this approach for ECS :-) : https://github.com/hyperdxio/aws-ecs-opentelemetry-sidecar/tree/main/examples

project0 avatar Aug 19 '24 06:08 project0