#50133 RFE - improve unindexed search information in the access log
Closed: wontfix by spichugi. Opened by mreynolds.

Issue Description

When an unindexed search, or an unindexed search component, is used we log notes=A (for fully unindexed), or notes=U(unindexed filter component) in the access log.

Notes=U is the tricky one because it's not always "bad", but it should be investigated none the less.

One way to help troubleshoot/investigate notes=A/notes=U would be add more info to the message about what attributes in the filter were unindexed (and why? No index or id scan limit exceeded).

The format could be something like:

notes=U[<list of unindexed attributes>]
notes=U[objectclass(missing index), mail(exceeded id scan limit)]

Or even do a dictionary format for easier parsing by external tools:

notes=U{<dict of unindexed attributes>}
notes=U{objectclass: missing index, mail: exceeded id scan limit}

We could also add a new access logging level to trigger this extra info, but if there isn't much overhead to doing it then it should be logged by default (no special log level).


I think this looks great! This is exactly what I had in mind. My concern still is that in notes=U we still shouldn't list objectClass=* since that's intended to be unindexed, but this change would be a huge improvement for debugging performance issues :)

Metadata Update from @firstyear:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.1

Metadata Update from @mreynolds:
- Issue priority set to: normal
- Issue set to the milestone: 1.4.3 (was: 1.4.1)

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.4 (was: 1.4.3)

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/3192

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.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

Metadata