Closed kford-newrelic closed 9 months ago
Not able to target for Apr-Jun timeframe; will consider for future quarter.
Migrated to Jira (https://issues.newrelic.com/browse/NR-24597). Targeted for next quarter's agent roadmap.
Should target the latest version
Because of the changes in the 4.x version of vertx, 2 new instrumentation modules will be needed:
Since Vert.x 4 ( https://vertx-web-site.github.io/) will be launched soon it would be nice if Java agent is updated. Currently it only supports up to 3.8.X
The agent automatically instruments Vert.x monitoring for Vert.x versions 3.2.0 to 3.8.3 according to this https://docs.newrelic.com/docs/agents/java-agent/getting-started/compatibility-requirements-java-agent
Need to also determine whether it's feasible to support 3.9.x versions too, for completeness
Example problem scenario today : customer has three(x3) verticles as :
(vertx) Variables
a) V1 - web verticle , an interface to the HTTP request, e.g. /getOrders /makeOrder
e.g. Service: order-management-production
Transaction : /health (GET)
=> makes synchronous and asynchronous calls between verticals. each vertical is running as a separate node.
-> V2 getTheUser()
-> V3 validateUsers()
b) No visibility once a vertical splits into a new vertical (e.g. V2, or V3) -> request visibility jumps from incoming HTTP request straight to DB metrics
Aha! Link: https://newrelic.aha.io/features/JAVA-211