Dump task driver panics in more log levels
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
### Nomad version
0.9.3
### Operating system and Environment details
Ubuntu 18.04.2 LTS
### Issue
When running our custom task driver, we noticed if the driver panicked (due to a bug in our own code), the backtrace will not be printed unless were using nomad's DEBUG log level. In my opinion, these logs are at minimum for the ERROR log level and should show up even when using INFO.
### Reproduction steps
Create a panicking task driver, run a task on it on a nomad with the log level set to INFO.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the issue with a panicking task driver while Nomad runs at INFO level, then trace where the driver panic backtrace is logged. Done means the backtrace appears at ERROR and INFO levels as intended, with the behavior verified using the reported reproduction steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100