As an alternative to ticket47982, the ability to configure 389 to send all logs to syslog would simplify the consolidation of logs on a central server.
This would be a configurable option by the user and would be separate to the named-pipe logging in my view. Buffering would be unnecessary/unwanted in this context so that rsyslog (for example) can populate the timegenerated property appropriately.
Having the ability to log directly to syslog or systemd-journal will simplify the task of consolidating logs on a central server.
An added bonus with using systemd-journal would be the ability to break out log data into key/value pairs for inclusion in the logs. This would provide a rich method of searching dirsrv logs for specific data.
Could this ticket be combined with "Ticket #47968 - [RFE] Send logs to journald"?
Replying to [comment:2 nhosoi]:
Yes, because how does one "send logs to journald" if not via the same syslog (man 3 syslog) interface? Unless there is some sort of separate "journald api" that I am not aware of.
Appologies - didn't (a) notice Ticket#47968 or (b) know that the same syslog interface is used in both cases.
Be as well closing this ticket - I'll track 47968 instead.
Metadata Update from @nhosoi: - Issue set to the milestone: N/A
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1314
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Duplicate)
Login to comment on this ticket.