[SERVER-84568] Include arbitrary mongot metadata in slow query log for $search and $vectorSearch Created: 04/Jan/24 Updated: 02/Feb/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Oren Ovadia | Assignee: | Vamsy Annabattula |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | qi-search | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Integration
|
| Participants: |
| Description |
|
When `mongot` cursor metadata contains a `slowQueryLog` field, this information should be integrated into the slow query log `mongot` section. This data would be unstructured (likely just a bson document) so that the search team can add to it without requiring the query team team to write explicit processing code that needs to be backported to other versions. On the search side the first planned use is to pass back `metadata.count.lowerBound` and `metadata.count.total` information about doc matches as this strongly correlated with high latency – it is similar to mongod's `examined`.
CC: trevor.mcculloch@mongodb.com , ted.tuckman@mongodb.com |
| Comments |
| Comment by Oren Ovadia [ 04/Jan/24 ] |
|
I like Trevor's idea of passing an unstructured blob there |