You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm running otel collector as a sidecar in ECS scheduled task.
I'm using awsfirelens log driver in and use fluentforward receiver in the otel collector.
When I run a hello-world container as a scheduled task (which task finished in a mili-second because just printing hello world), otel collector sidecar gracefully shutdown so fast and I'm missing scheduled task logs.
Describe the solution you'd like
Before starting shutdown, i would like to able to configure otel to wait X more seconds after it get SIGTERM signal.
Describe alternatives you've considered
Container dependency options does not cover for shutdown.
Additional context
As result of this, we have to use fluentbit sidecar. Because it has a configuration named flush which allow us to get logs even for hello world scheduled task.
The text was updated successfully, but these errors were encountered:
Component(s)
No response
Is your feature request related to a problem? Please describe.
I'm running otel collector as a sidecar in ECS scheduled task.
I'm using
awsfirelens
log driver in and usefluentforward
receiver in the otel collector.When I run a hello-world container as a scheduled task (which task finished in a mili-second because just printing hello world), otel collector sidecar gracefully shutdown so fast and I'm missing scheduled task logs.
Describe the solution you'd like
Before starting shutdown, i would like to able to configure otel to wait X more seconds after it get
SIGTERM
signal.Describe alternatives you've considered
Container dependency options does not cover for shutdown.
Additional context
As result of this, we have to use
fluentbit
sidecar. Because it has a configuration namedflush
which allow us to get logs even for hello world scheduled task.The text was updated successfully, but these errors were encountered: