MongoDB instrumentation won't apply to the sync client if async/reactivestreams client is also present

[jasonjkeller]

MongoDB instrumentation won't apply to the sync client if async/reactivestreams client is also present.

This was an unexpected consequence of changes that were released in agent 7.4.0 in an effort to prevent the MongoDB instrumentation from applying to the async/reactivestreams client because it was causing token timeouts and incorrect query response times.

For context: #198 (comment)

If only the sync client is present then the instrumentation should still apply.

One workaround is to roll back to agent 7.3.0 until this can be addressed in a new release.

Related to: #198

[pmthortful]

Hi,

Just wanted to flag that we are experiencing this issue, and due to not wanting to be on an old version of the agent due to the recent log4j vulnerability, we currently have 0 visibility on our mongo database operations

[kford-newrelic]

Hi @pmthortful , while not ideal, if this issue is significantly impacting you, you could rollback to the 7.3.0 agent and disable agent logging (to compensate for the log4j vulnerability). This isn't ideal because if you have any static code scans going, the 7.3.0 release will show up but it's relatively straightforward to confirm that agent logging is turned OFF.

[jasonjkeller]

@pmthortful I've submitted a PR that should restore visibility into MongoDB queries that is planned to be in our next release coming out in the next week or so (which will also have the latest Log4j patches included).