Skip to content

Ability to configure otel to wait for a desired duration after the SIGTERM signal #34054

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

Closed
realsby opened this issue Jul 12, 2024 · 4 comments
Closed

Comments

@realsby
Copy link

realsby commented Jul 12, 2024

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

Copy link
Contributor

Pinging code owners for receiver/fluentforward: @dmitryax. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@atoulme
Copy link
Contributor

atoulme commented Oct 12, 2024

This seems like a possible option for fluentforwardreceiver to have a wait before shutting down.

@atoulme atoulme removed the needs triage New item requiring triage label Oct 12, 2024
Copy link
Contributor

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Dec 11, 2024
Copy link
Contributor

github-actions bot commented Feb 9, 2025

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants