Logging information helps us to find the root cause queries to confirm and reproduce an underlying bug. In an incident like SERVER-83091 where there's a thread causing the mongod to hang indefinitely, we would like to know the shape of the underlying query causing the issue and how to reproduce that consistently within a short time.

Currently, we have logging for slow queries and printAllThreadStacks for this purpose. However, the former one only prints upon the completion of a query, while the latter prints the stack trace with limited information about the query shapes.

This ticket proposes to log the in-progress queries whenever printAllThreadStacks is called such that we are able to see the underlying queries contributing the those stack traces.