Learn more about these different git repos.
Other Git URLs
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. Examples of the extra fields are source file, line or SSSD domain.
There might even be a performance enhancement as SSSD had to perform an fsync() after each debug line, although I haven't done any measurements.
summary: RFE: Send debug logs to journald by default => [RFE] Send debug logs to journald by default
milestone: NEEDS_TRIAGE => SSSD 1.12 beta
rhbz: => todo
patch: 0 => 1
The patches landed upstream, so far the journal must be enabled by the admin by editing /etc/systemd/system/sssd.service.d/journal.conf, restarting systemd and then sssd.
owner: somebody => sgallagh
resolution: => fixed
status: new => closed
changelog: => SSSD is now able to send structured debug logs to journald, tagged with the code file, line number and domain that the log pertains to. To enable this functionality, SSSD must be configured at build-time with --with-syslog=journald and must be launched without -f/--debug-to-files
design: => N/A (trivial)
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1115508
rhbz: todo => [https://bugzilla.redhat.com/show_bug.cgi?id=1115508 1115508]
Metadata Update from @jhrozek:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.12 beta
SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
to comment on this ticket.