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

Include stdour/stderr crashlog in email #134

Open
mrx23dot opened this issue Jan 7, 2024 · 0 comments
Open

Include stdour/stderr crashlog in email #134

mrx23dot opened this issue Jan 7, 2024 · 0 comments

Comments

@mrx23dot
Copy link

mrx23dot commented Jan 7, 2024

It would be great to see how the program died.
Usually there is a stack trace on stderr.

Currently supervisord restarts task and I'm getting email
Process xxx in group xxx exited unexpectedly (pid 416525) from state RUNNING

which is not useful, then I login and ask for current output but it's long ovewritten by new instance.

So it would be great to include tails into email (like 20lines each), we shouldn't get many emails in the first place, but when we do it should contain very useful info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant