Add postfiltering logging to api/issues

What does this MR do and why?

Add postfiltering logging to api/issues

While working on Draft: Introduce FinderResultsLogger for analysis (!215674) I noticed that writing a logger to fit any Finder with who knows what kinda params is hard. You can see the serialization/deserialization stuff consuming most of the MR. Here's a cheaper approach where post-filtering is already existing where we can measure performance and accuracy.

Lets collect postfiltering performance and prefiltering accuracy data to help guide us where to invest in our authorization efforts.

  • introduce postfilter_logging flag
  • introduce PostfilteringHelpers

part of: https://gitlab.com/gitlab-org/gitlab/-/work_items/581753

References

Screenshots or screen recordings

Before After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Jay

Merge request reports

Loading