Add ability to upload backtrace as file
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 25
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Some logging systems will garble or incorrectly sort the backtrace output that logbt returns if simply pushed to stdout/stderr. So, to workaround this problem and to provide the easy ability to look at a group of backtraces in one place, logbt could gain the ability to upload backtraces to a specific location on s3.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing logbt's current stdout/stderr backtrace output and its existing command-line options; the issue names no files or tests. Done means logbt can upload backtraces to a specified S3 location so logging systems do not garble or reorder them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, shell
- Domain
- cli, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100