[Feature Request] documentation for logging

[ReneHezser]

In my Docker Compose setup, I'd like to understand how some things are working.

Digging through the dockerfile files, I found that some images are using the env variable PAPERMERGE__MAIN__LOGGING_CFG to configure the logging configuration. Therefore, I did this:

papermerge:
  image: papermerge/papermerge:3.4.1
  container_name: papermerge
  environment:
    ...
    PAPERMERGE__MAIN__LOGGING_CFG: /logs/logging.yaml
    volumes:
      ...
      - /.../papermerge/logs:/logs
    ...

papermerge-i3worker:
  image: papermerge/i3worker:0.3
  container_name: papermerge-i3worker
  command: worker
  environment:
    PAPERMERGE__SEARCH__URL: solr://papermerge-solr:8983/pmg
    PAPERMERGE__REDIS__URL: redis://papermerge-redis:6379/0
    I3_WORKER_ARGS: "-Q i3 -c 2"
    PAPERMERGE__MAIN__LOGGING_CFG: /logs/logging.yaml
  depends_on:
    - papermerge-redis
    - papermerge-solr
  volumes:
    - /.../papermerge/logs:/logs

My logging.yaml looks like this:

version: 1
disable_existing_loggers: false

formatters:
  verbose:
    format: '%(levelname)s %(asctime)s %(module)s %(message)s'

handlers:
  console:
    level: INFO
    class: logging.StreamHandler
    formatter: verbose

loggers:
  papermerge.core:
    level: INFO
    handlers: [console]
    propagate: no
  auth_server:
    level: INFO
    handlers: [console]
  papermerge.search:
    level: INFO
    handlers: [console]
    propagate: no
  papermerge.search.tasks:
    level: INFO
    handlers: [console]
    propagate: no
  ocrworker.tasks:
    level: DEBUG
    handlers: [console]
  i3worker:
    level: INFO
    handlers: [console]
  path_tmpl_worker:
    level: DEBUG
    handlers: [ console ]
  celery:
    level: INFO
    handlers: [console]