Export env vars logging Erlang crash dumps #3649
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Summary
What and Why:
This will output Erlang crash dumps to stderr, rather than to an erl_crash.dump file.
Many folks run into issues trying to debug an Elixir application that is crashing and the logs output this:
Because our machines are ephemeral, this is cleared immediately and there's no way get the file without doing shenanigans with your Dockerfile. Now you have minimal shenanigans to get the info via
fly logs
.How:
Environment variable exports
Related to:
https://community.fly.io/t/how-to-read-erl-crash-dump/20404?u=morzaram
Documentation