Add new instrumentation for MongoDB reactive streams driver 4.2.x+

Recently added mongodb-async instrumentation supports up to, but not including, mongodb reactive streams driver 4.2.x.

https://github.com/newrelic/newrelic-java-agent/blob/253fccdfcf5db8698c263126b0b35742a69283af/instrumentation/mongodb-async-4.0/build.gradle#L20

Starting with the MongoDB reactive streams driver 4.2.x, the mongo driver was refactored and our existing instrumentation no longer applies. We will need to add a new mongodb-async-4.2 instrumentation module.

https://github.com/mongodb/mongo-java-driver/tree/4.2.x/driver-reactive-streams

(Migrate to Jira)

[Stephan202]

@kford-newrelic I hate to be “that guy”, but the decision to defer resolution of this issue is even more disappointing than the decision to close #725.

As it stands (and as shared in earlier support ticket(s) and with our account manager) the New Relic Java Agent doesn’t report on almost any of the MongoDB queries performed by some of our most important deployments. The few queries that do still show up in the UI are due to legacy code using Jongo, which we’re actively migrating to the reactive driver. Right now we’re effectively blind when it comes to key database usage.

As also shared in the other ticket, this functionaliy, too, “just works” with the OpenTelemetry Java Agent.

For us the issue with MongoDB observability started back when we used MongoDB driver 3.x. These days we use 4.x, and despite that major version line being nearly 2.5 years old, it is still not properly supported by the New Relic Java Agent. (As the ticket summary states, the 4.0 line is currently supported, but the most recent 4.0.x driver release was over 1.5 years ago; by now we’re on 4.7.x. We generally upgrade our dependencies within a month of release.)

This is a driver for one of the most popular DBs in the world, and New Relic wants to be the leading observability platform. As a customer it’s hard to understand how supporting this cannot be a priority.

[kford-newrelic]

@Stephan202 no worries - your feedback is important to us and you’re sharing it in a respectful way intended to help us improve our products, so it’s all good!

Let me bring this back to the team - let’s see what we can do…