This request is for an addition to the slow query message. SERVER-63642 implemented a serverStatus metric for this. Currently, the time spent planning a query is unaccounted in both the slow log line and in serverStats. Note that SERVER-68029 tracks very related work for the cost-based optimizer.

Having a metric in server status reflecting the time spent planning queries would give a strong signal if there is something wrong. Perhaps a metric like "timeAcquiringMicros" for the locking statistics would be helpful to determine how efficient planning is.

Reporting the time spent planning a query in the slow query message would greatly assist query diagnostics. Currently a query taking excessive time planning will not reflect in any of the current metrics, hiding any potential impact from planning delays.