django-DefectDojo icon indicating copy to clipboard operation
django-DefectDojo copied to clipboard

Logs are written to stderr

Open joeppeeters opened this issue 1 year ago • 1 comments

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.

Screenshot 2023-05-16 at 17 38 35

Steps to reproduce Steps to reproduce the behaviour based on a clean checkout of this repo running on OSX:

  1. Start dojo by: ./dc-up.sh
  2. Tail logs, filter stdout only: docker logs django-defectdojo-uwsgi-1 -f 2>/dev/null
  3. Notice logs are empty
  4. Tail logs, filter stderr only: docker logs django-defectdojo-uwsgi-1 -f 1>/dev/null
  5. 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

joeppeeters avatar May 17 '23 09:05 joeppeeters