This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2284623 - [RFE] Structured (JSON) logging option for RHDS access and error logs
Summary: [RFE] Structured (JSON) logging option for RHDS access and error logs
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: 389-ds-base
Version: 11.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: LDAP Maintainers
QA Contact: LDAP QA Team
Evgenia Martynyuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-06-03 17:06 UTC by Chance Callahan
Modified: 2024-06-26 13:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-26 13:51:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   DIRSRV-68 0 None None Red Hat Issue Tracker 2024-06-26 13:51:51 UTC

Description Chance Callahan 2024-06-03 17:06:10 UTC 
(Copied from case verbatim)

Given the newer security log is in a JSON format, could we consider an optional access logging format that would consolidate relevant log information into a structured format? I wouldn't even necessarily suggest this become a default change, but first an option to change to this style of logging.

Example: If there is RESULT entry from a bind failure, I have to find the corresponding BIND operation line to find the DN, and then find the first line for the host's "conn=" to find the source IP. Having certain details repeated (like the connection IP in addition to the internal connection number), is a substantial improvement in usability at the cost of some increased disk IO and storage.

(Simiarly, high etime (unindexed) searches can have many other log entries between the SRCH line and the RESULT line.)
Comment 1 Viktor Ashirov 2024-06-26 13:51:52 UTC 
This BZ has been automatically migrated to Red Hat Issue Tracker https://issues.redhat.com/browse/DIRSRV-68. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.