RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1168956 - [RFE] Send logs to journald
Summary: [RFE] Send logs to journald
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: httpd
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Luboš Uhliarik
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On: 963620
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-28 14:09 UTC by Martin Kosek
Modified: 2017-07-13 15:05 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-13 15:05:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Martin Kosek 2014-11-28 14:09:02 UTC
Description of problem:

Instead of writing the debug logs directly to the disk, it is possible to send them to journald, on platforms where journald is available.

The biggest benefit is that the debug logs are structured, so it's possible to decorate the debug messages with key/value pairs and later query based on these extra fields.

This feature is a required so that FreeIPA project can implement additional log processing or auditing capabilities. See upstream ticket for details: ​https://fedorahosted.org/freeipa/ticket/4296.

Comment 1 Jan Kaluža 2015-02-18 08:24:59 UTC
We could backport this feature, but there's big performance hit when logging anything except error_log with LogLevel warn to journald. See Bug 963620.

Comment 3 Jan Kaluža 2015-04-29 09:09:12 UTC
Note that even for high LogLevel, this could make DoS attacks easier for an attacker who would generate requests which would trigger per-request error in the error_log.

Comment 5 Martin Kosek 2015-05-05 09:59:40 UTC
For FreeIPA centralized logging capabilities, it would be very useful to send all logs in structured format, i.e. both access log and error log. Then the logs could be sent as JSON to some central ELK-like log processing node without additional parsing rules that would make the text->structure conversation on the server side.

The performance gap of course limits the usability greatly on affected systems. However, I still think it would make sense to have an opt-in support for it so that people interested in journald logging and which do not have that big load may switch it on. The benefit here would be that it would be another use case missing in journald and that put some weight on Jan's patches.

That said, I do not see that change as high priority for next minor RHEL release if you are out of resources, but I still see it as useful forward looking addition.

Comment 8 Joe Orton 2017-02-07 08:58:31 UTC
We can keep this open but ultimately nothing is going to happen here unless somebody puts some effort on the journald/kernel-side performance stuff (SCM_CGROUP).

Comment 10 Joe Orton 2017-07-13 15:05:50 UTC
Unless this is going to be set as a priority for fixing across journald & the kernel, we're not to address this in httpd.


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