When adding a bulkWrite test case to jstests/sharding/read_write_concern_defaults_application.js as added in SERVER-45693 I found that I could not test bulkWrite via profiler output.

We should figure out what the desired profiler behavior is for the command and see if we need to make any changes.

SERVER-23266 discusses the inconsistent state of profiling for other batch write commands (as of 2016 anyway).