Learn more about these different git repos.
Other Git URLs
It would be extremely helpful if sssd had a transaction or correlation id associated with the log entries.
When debugging issues on a busy system, messages from various transactions get interleaved making it very difficult to identify related entries (especially with higher logging levels). It appears there may already be an id that facilitates cross log correlation but if I am misreading those messages, it would be helpful to have that as well (or share the transaction id across logs)
I agree this would be helpful and it's something we've been talking about for some time. But it's really non-trivial effort.
At the moment, I'm moving the bug into the Future releases milestone, so it will be considered when we plan another release.
Of course, patches or concrete ideas how to implement this are welcome.
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Future releases (no date set yet)
Not sure how helpful this is but http://opentracing.io/ might be useful.
Metadata Update from @thalman: - Issue tagged with: Future milestone
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: - https://github.com/SSSD/sssd/issues/4532
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 @pbrezina: - Issue close_status updated to: cloned-to-github - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.