Bug 1196754 - [RFE] Write structured Satellite 6 logs to journald
Summary: [RFE] Write structured Satellite 6 logs to journald
Keywords:
Status: CLOSED DUPLICATE of bug 1163020
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Other
Version: Unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-26 16:30 UTC by Chris Roberts
Modified: 2019-08-15 04:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-17 18:08:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Chris Roberts 2015-02-26 16:30:51 UTC
1. Proposed title of this feature request

[RFE] Write structured logs to journald

2. <INTERNAL>

3. What is the nature and description of the request?

To ensure that all logging done by Satellite 6 is done natively and in a structured manner to journald wherever possible.

4. List business requirements here

Structured logging is a key benefit that journald brings to Admins.  The ability to easily search, sort, and parse logs (especially once centralised) makes the job of administering any system easier.  Whilst this functionality could (should?) be applied to every application that Red Hat ships, I am raising this specifically against Satellite 6.x at the moment.

5. How would the customer like to achieve this?

All components of Satellite 6.x should log natively to journald in a structured format.  Logs could optionally be written to application log files, but I think this would be a waste of time.

6. Specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

`journalctl -f` will display all new log entries arriving at journald.  Search around /var/log for katello/foreman/pulp/candlepin/etc logs - there should be none.

7. Is there already an existing RFE upstream or in bugzilla?

For Katello & Foreman, yes - http://projects.theforeman.org/issues/9560 & http://projects.theforeman.org/issues/9561
For Pulp, Candlepin and the rest, no

8. Does the customer have any specific timeline dependencies and which release would they like to target?

Satellite 6.1 would be nice, but this may have branched already.  If it's too late for 6.1, it should be a strong candidate for 6.2

9. <INTERNAL>

10. List any affected packages or components.

All logging components of Foreman, Katello, Pulp, Candlepin, Puppet, etc

11. Would the customer be able to assist in testing this functionality if implemented?

Yes

Comment 1 RHEL Program Management 2015-02-26 20:17:40 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 4 Bryan Kearney 2015-04-17 18:08:21 UTC

*** This bug has been marked as a duplicate of bug 1163020 ***


Note You need to log in before you can comment on or make changes to this bug.