Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionRiccardo Furlan
2022-10-21 10:29:06 UTC
This bug was initially created as a copy of Bug #1925559 in order to achieve a backport to Red Hat Enterprise Linux 8 as well.
Description of problem:
A customer had an issue for which the sssd queries were taking 2.5 seconds to be fulfilled, while the usual time in their environment was 0.1 seconds.
In the sssd logs they were not able to spot any problem on the LDAP backend.
The customer would like to introduce a timer for any LDAP query, which should be written in the debug logs (correct debug level to be identified).
They would like also to have these queries logged into the sssd with a warning level (lower than debug) once the time taken is really high (eg 5 seconds).
The time for which the logs should be written in warning level in place of debug level should be configurable.
This would help the debug of the LDAP backend during incidents (eg network or LDAP backend overload/service disruption) and to identify deviation from the regular query time from a given server.
bonus: this metric could be useful also for the PCP project.
Version-Release number of selected component (if applicable):
How reproducible:
Introduce a network latency or LDAP backend latency between sssd and LDAP backends.
Steps to Reproduce:
1. introduce a network latency or LDAP backend latency between sssd and LDAP backends
2. increment the logs to debug=9
3. check the sssd logs
Actual results:
No information over the time taken for a given query
Expected results:
Query time is written in the debug logs,
Long time queries written in the regular logs.