maxTimeMS() for every find query
Enable a preference option to concatenate .maxTimeMS("your value") on each find query. To avoid misspelled queries to bring down the database.
Kai Virkki commented
This one would be awesome to have as it's always a hassle to figure out which replicaset member the query is running on, to find the opId and call db.killOp() for it.
And it's super-easy to make queries that cause collection scans :(
Marcus Connolly commented
This is especially important on sharded clusters where users abort a query via their mongos connection, which only aborts the query on the client side, yet continues to run on each shard's mongod underneath. Having the ability to set a maxTimeMS by default would solve this.