Can you elaborate on what you mean by this? Are you referring to analysing or decoding packets over the wire? WireShark passively captures/analyses network traffic so shouldn’t interfere with client compatibility.
Given the description of an
insert command not working, it sounds like you perhaps are developing a proxy which isn’t relaying commands/responses as expected. I would normally recommend a tool like WireShark to inspect the network communication and determine what is different between your working driver environment and the
mongo shell ;-).
What specific version of the
mongo shell and server are you using (as reported by
db.version()) and how are you detecting that the
insert command is not sent? What is the result in the
If you are developing something like a proxy, can you confirm how you are altering the wire protocol communication and what version(s) of the wire protocol you are supporting?
mongo shell relies on the wire protocol version for context on the connected server which may also alter the message sent (for example, older servers do not support the modern
OP_MSG opcode). Modern versions of the
mongo shell also convert inserts into bulk write commands, so you may not see an
insert command if you are filtering network traffic to an expected opcode.