Right now we only track opcounters at a instance level. Some customers may want to break this down at a database level to e.g. identify which database(s) are under the most load.

Potential workarounds have been discussed. Tailing the oplog only tracks writes, not reads. To track reads the customer would need to turn on profiling, which can cause issues with performance.