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

server crash logging/reporting and crash queue maintenance / rollup #38

Open
arcolife opened this issue Jul 16, 2018 · 0 comments
Open
Assignees
Labels
B-level slightly non-trivial with intermediate difficulty enhancement New feature or request exception-handling debugging
Milestone

Comments

@arcolife
Copy link
Collaborator

arcolife commented Jul 16, 2018

if server crashes, we need (WAL) to notify and dump env vars/tracebacks and report it. And then use that dump for patched releases.

think: open tracing / airbrake / honeybadger

cc/ @miamiruby

Also, add airlog explicit log level handing flag/config param; obfuscate sensitive info in dump.

@arcolife arcolife added enhancement New feature or request B-level slightly non-trivial with intermediate difficulty labels Jul 16, 2018
@arcolife arcolife added this to the Alpha 2 milestone Jul 16, 2018
@arcolife arcolife added the exception-handling debugging label Jul 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B-level slightly non-trivial with intermediate difficulty enhancement New feature or request exception-handling debugging
Projects
None yet
Development

No branches or pull requests

2 participants