At present the shards are producing warnings flagging the WouldChangeOwningShard error whenever an operation attempts to change the document's shard key:

{
	"t" : {
		"$date" : "2024-12-05T13:42:20.276+11:00"
	},
	"s" : "W",
	"c" : "WRITE",
	"id" : 7267501,
	"svc" : "S",
	"ctx" : "conn35",
	"msg" : "Plan executor error",
	"attr" : {
		"operation" : "findAndModify",
		"error" : {
			"code" : 283,
			"codeName" : "WouldChangeOwningShard",
			"errmsg" : "This update would cause the doc to change owning shards",
			"preImage" : {
				"_id" : {
					"$oid" : "67510dcdb7a0f6e4723a214f"
				},
				"a" : 0
			},
			"postImage" : {
				"_id" : {
					"$oid" : "67510dcdb7a0f6e4723a214f"
				},
				"a" : 3
			},
			"shouldUpsert" : false
		},
<...>

Most of the time these events are invisible for users as the cluster is able to self-resolve these operations via use of implicit (internal) transactions.

However, the users can get easily spooked due to the log entries being a warning about an error. These messages would also inflate the log output if the amount of operations of that kind is large.

Would it be possible to suppress these messages by default so these could only become visible with increased (non-default) log verbosity?