Feature #10487
As a developer, I should be able to define custom loggers and control them via settings
Related issues
Associated revisions
refs #10487 - add logging.yaml to /etc/foreman
refs #10487 - add logging.yaml to /etc/foreman
Remove copies of Foreman configs and instead copy the shipped examples.
History
#1
Updated by The Foreman Bot almost 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2376 added
- Pull request deleted (
)
#2
Updated by Ohad Levy almost 8 years ago
- Related to Feature #7033: Syslog capability added
#3
Updated by Dominic Cleal almost 8 years ago
- Category set to Rails
- Assignee set to Eric Helms
- Legacy Backlogs Release (now unused) set to 35
#4
Updated by Eric Helms almost 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 3088e6415fb94b9953db993800463f1d5862309f.
#5
Updated by Dominic Cleal almost 8 years ago
- Related to Refactor #10711: Move LDAP instrumentation to its own logger added
#6
Updated by Dominic Cleal almost 8 years ago
- Has duplicate Feature #6524: log settings should be part of /etc/foreman/settings added
#7
Updated by Lukas Zapletal about 7 years ago
- Related to Feature #13702: Configure Foreman with syslog by default added
Fixes #10487: Add custom logging support
This change moves away from the Rails logger to the 'logging' gem
to support more configurability of logging. Further, this allows for
the creation of custom loggers that plugins can then create during
registration (with `logger`) or through settings.
For example, the plugin katello could define within its settings file
(settings.plugins.d/katello.yaml) the following:
```
:katello:
:loggers:
:pulp_rest:
:enabled: false
:cp_rest:
:enabled: true
```
Which would define 2 loggers, pulp_rest and cp_rest where the latter
is turned on be default, but the former can be enabled such that
the log file isn't continuously filled with messages from that particular
layer.