Project

General

Profile

Actions

Feature #10487

closed

As a developer, I should be able to define custom loggers and control them via settings

Added by Eric Helms about 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Rails
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Related issues 4 (0 open4 closed)

Related to Foreman - Feature #7033: Syslog capabilityDuplicate08/12/2014Actions
Related to Foreman - Refactor #10711: Move LDAP instrumentation to its own loggerClosedDominic Cleal06/05/2015Actions
Related to Foreman - Feature #13702: Configure Foreman with syslog by defaultDuplicate02/15/2016Actions
Has duplicate Foreman - Feature #6524: log settings should be part of /etc/foreman/settingsClosed07/08/2014Actions
Actions #1

Updated by The Foreman Bot about 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2376 added
  • Pull request deleted ()
Actions #2

Updated by Ohad Levy about 9 years ago

Actions #3

Updated by Dominic Cleal about 9 years ago

  • Category set to Rails
  • Assignee set to Eric Helms
  • translation missing: en.field_release set to 35
Actions #4

Updated by Eric Helms about 9 years ago

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

Updated by Dominic Cleal about 9 years ago

  • Related to Refactor #10711: Move LDAP instrumentation to its own logger added
Actions #6

Updated by Dominic Cleal about 9 years ago

  • Has duplicate Feature #6524: log settings should be part of /etc/foreman/settings added
Actions #7

Updated by Lukas Zapletal over 8 years ago

  • Related to Feature #13702: Configure Foreman with syslog by default added
Actions

Also available in: Atom PDF