django-DefectDojo
django-DefectDojo copied to clipboard
Logs are written to stderr
Most logs (all?) seem to be send to /dev/stderr
.
After deploying DefectDojo on our Nomad infra it appeared quite noisy on our error monitoring. After investigation it seems to send a lot of (info level?) logs to the error device.
Steps to reproduce Steps to reproduce the behaviour based on a clean checkout of this repo running on OSX:
- Start dojo by:
./dc-up.sh
- Tail logs, filter stdout only:
docker logs django-defectdojo-uwsgi-1 -f 2>/dev/null
- Notice logs are empty
- Tail logs, filter stderr only:
docker logs django-defectdojo-uwsgi-1 -f 1>/dev/null
- Notice logs come in
Expected behavior Logs are send to the correct device
Deployment method (select with an X
)
- [x] Docker Compose (presumably not relevant)
- [x] Nomad
- [ ] Kubernetes
- [ ] GoDojo
Environment information
- Operating System: replay scenario on OSX
- DefectDojo version:
v2.22.2
,master
(6e0d765bfd6aff96200a6dc788d3a84c05e79bd7)
Observations
affected containers:
-
django-defectdojo-uwsgi-1
-
django-defectdojo-celerybeat-1
-
django-defectdojo-celeryworker-1
expected behaviour on containers:
-
django-defectdojo-nginx-1
-
django-defectdojo-mysql-1
-
django-defectdojo-rabbitmq-1
which points to the Django/Python config?
Other sources
- Thread on Slack
- Similar symptoms described on Stackoverflow