Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Galaxy logging #1351

Merged
merged 8 commits into from
Nov 19, 2018
Merged

Conversation

cutwater
Copy link
Collaborator

Backport: #1342

(cherry picked from commit ec34bd3)
(cherry picked from commit bb9cf03)
* Logging configuration at the bottom of settings file due to its size.
* Remove duplicated filter `request_id` from production settings.
* Fix typo in `django.request` handler.

(cherry picked from commit b386b03)
Relative module names are non informative. Since Galaxy uses
loggers based on module name, logger name reflects module and
gives fully qualified name.

(cherry picked from commit a06a955)
* Explicit `django.db` logger is not needed as it's handled
  by 'django' logger.
* The logger `django.request` duplicates django's
  builtin configuration [1]. By default django sends all `ERRROR`
  and `CRITICAL` messages to the `AdminEmailHandle` in `DEBUG=False`
  mode.
* Remove explicit `propagate=True`, since child loggers propagate
  log messages to parent loggers by default.
* Remove allauth debug logger.

(cherry picked from commit 0227513)
* Aggregate multiple specific logger configurations
  into single global `galaxy` configuration.
* Set minimal log level `WARNING` for production environment.

Implications:

Due to project structure and celery architecture all worker
messages have to be handled by `galaxy` worker and should not
be propagated to root logger, that is patched by `celery`.
As a result celery log message format is sligtly different from
the galaxy one.
To be fixed in future patches.

(cherry picked from commit e20539f)
* Disable autoreload.
* Set minimal log level to `WARNING`.

(cherry picked from commit 3869d71)
@cutwater cutwater added the backport Backport pull request label Nov 16, 2018
@cutwater cutwater added this to the 3.1.1 milestone Nov 16, 2018
@cutwater cutwater merged commit 27e2ecd into ansible:stable/3.1 Nov 19, 2018
@cutwater cutwater deleted the backport/3.1/1342 branch November 19, 2018 11:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Backport pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant