Project

General

Profile

Actions

Feature #22493

closed

Add new logging options to integrate with logging-journald gem

Added by Lukas Zapletal about 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Logging
Target version:

Description

Foreman uses logging gem for all logging, this has new plugin which enables structured logging into system journal (https://github.com/lzap/logging-journald). This feature will add configuration options to use the logging plugin.

Foreman already uses MDC (mapped diagnostic context) for session/request id. As part of this effort, we will add more MDC flags which are logged as structured fields in journald:

  • logger name
  • user login
  • organization label
  • location label
  • request id
  • session id (safe only)
  • remote ip address

As part of this, logging-journald will become hard dependency of foreman-core. Nothing is changing for development logging configuration, but for production we will make changes in the installer to send logs into journald and splitting them via rsyslog back into production.log for easier transition for existing users and tools. To be able to do that, all logs will be sent to facility local6 (configurable option).

Further reading:


Related issues 4 (1 open3 closed)

Related to Installer - Feature #22559: Configure foreman to log to system journalClosedEwoud Kohl van WijngaardenActions
Related to Foreman - Tracker #22569: Unified and structured loggingAssignedLukas Zapletal

Actions
Related to Foreman - Feature #3861: Better logging/reporting/audit of provisioning including contentsResolvedLukas Zapletal12/12/2013Actions
Related to Foreman - Bug #26039: Templates are getting rendered in production.logClosedLukas ZapletalActions
Actions #1

Updated by Lukas Zapletal about 6 years ago

  • Description updated (diff)
Actions #2

Updated by The Foreman Bot about 6 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/5237 added
Actions #3

Updated by Lukas Zapletal about 6 years ago

  • Related to Feature #22559: Configure foreman to log to system journal added
Actions #4

Updated by Lukas Zapletal about 6 years ago

Actions #5

Updated by Lukas Zapletal almost 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #6

Updated by Marek Hulán almost 6 years ago

  • translation missing: en.field_release set to 330
Actions #7

Updated by The Foreman Bot almost 6 years ago

  • Pull request https://github.com/theforeman/foreman/pull/5339 added
Actions #8

Updated by The Foreman Bot almost 6 years ago

  • Pull request https://github.com/theforeman/puppet-foreman/pull/631 added
Actions #9

Updated by The Foreman Bot almost 6 years ago

  • Pull request https://github.com/theforeman/foreman/pull/5421 added
Actions #10

Updated by Lukas Zapletal over 5 years ago

  • Related to Feature #3861: Better logging/reporting/audit of provisioning including contents added
Actions #11

Updated by Tomer Brisker about 5 years ago

  • Related to Bug #26039: Templates are getting rendered in production.log added
Actions

Also available in: Atom PDF