Skip to content
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

Capture stack traces of failed or killed containers #93

Open
iand opened this issue Sep 16, 2022 · 0 comments
Open

Capture stack traces of failed or killed containers #93

iand opened this issue Sep 16, 2022 · 0 comments

Comments

@iand
Copy link
Contributor

iand commented Sep 16, 2022

We probably already capture the stack trace when kubo fails due to a panic as part of the log. However we should check if this is actually captured or whether the container restarts before it can be send to cloudwatch.

Also we should try and capture a stack trace if the container is terminated due to OOM.

@iand iand added the unplanned label Sep 16, 2022
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

1 participant