Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • concrexit concrexit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • thaliathalia
  • concrexitconcrexit
  • Issues
  • #957
Closed
Open
Issue created Nov 03, 2019 by Jelle Besseling@jbesselingMaintainer

Logging format is not informative

One-sentence description

Both logfile logging and console logging are not very informative, for different reasons.

Why?

Because logfile logging has no format, only the message is printed without any context. logfile and console could both use the same logging format.

The %(module)s logging attribute does not print the fully qualified module name, just the top level name. This would be urls for the education.urls package. Instead the %(name)s attribute could be used, which will give the fully qualified package name when used in conjunction with logging.getLogger(__name__) (which we do everywhere already).

Furthermore we could drop %(process)d and %(thread)d, as we will probably never use those. Lastly, having the log level next to the message would make more sense, as in INFO The message, because that seems easier to read.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking