Actually the DB and the collection(s) would be a good start, but right now there is no chance to identify these queries but to log all queries to the profiler.
Especially on dev systems where the queries may not be slow (so profiler mode 1 with eg 50ms does not hit), but still not performant, the DB, collection and shape would be very good to get. This way queries can be optimized before getting into prod.
Actually the DB and the collection(s) would be a good start, but right now there is no chance to identify these queries but to log all queries to the profiler.
Especially on dev systems where the queries may not be slow (so profiler mode 1 with eg 50ms does not hit), but still not performant, the DB, collection and shape would be very good to get. This way queries can be optimized before getting into prod.