If you point me in the right direction I might be able to make these adjustments. I see https://github.com/Ironholds/floccus but that seems to be just the functions, and not the glue that gets run against the actual CirrusSearchRequests files.

Who is 'you'? Is Ironholds supposed to be CC'd here? What projects are supposed to be on this ticket?

An example of the logs to be processed: https://phabricator.wikimedia.org/P953

These are just the queries run as part of the browser tests, but might be a good enough sample to test against.

I ended up finding the code that does this, I'm pretty sure it is https://github.com/Ironholds/rainbow/blob/master/data_retrieval/core.py

I've got a patch worked up that should do the trick, but havn't fully tested yet.

I consider that it should work this way:

Before:

• User runs query A and gets 0 results and a search suggestion B. This is logged as a zero result query.
• User runs query B and gets results. This is not logged as a zero results query.

After:

• User runs query A. Backend sees 0 results and search suggestion B, runs search suggestion B, and gives that to the user. This is not logged as a zero results query.

I figure this is probably the way you've implemented it, but I wanted to make sure the requirements are clear.

Pushed patch to https://github.com/Ironholds/rainbow/pull/7

@EBernhardson is the log change now live?

@Ironholds not yet, someone needs to +2 the following patches:

Add executor id to CirrusSearchRequests log
https://gerrit.wikimedia.org/r/224502

Start internally forwarding/rewriting zero result queries with suggestions
https://gerrit.wikimedia.org/r/#/c/223885/

Is it done without those being merged and deployed? ;p

Yes, because the ticket says 'Update dashboards to handle' and the dashboards now appropriately handle the data. Getting the data into the dashboard is a tasked blocked by this one.

Now deployed!