-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to configure otel to wait for a desired duration after the SIGTERM signal #34054
Comments
Pinging code owners for receiver/fluentforward: @dmitryax. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This seems like a possible option for fluentforwardreceiver to have a wait before shutting down. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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: