VertX Experience

Hi,

See below a session export for one VertX transaction. You can see it is end to end.

Vertx.dts

I have a bigger export with more transactions. Please let me know if you need it.

Kind regards,

Chris

Got some purepaths to share? could be a nice blog story!

Hi Kristof,

I had the pleasure to instrument a Vertx application. In this post I would like to share my experiences.

Vertx is using the Async philosophy of NodeJS but in Java language. Vertx in my case was running in Amazon EC2.

We defined a custom entry point on the following method:

be.<customername>.common.http.vertx.yoke.routing.FlexibleRouter.handle(com.jetdrone.vertx.yoke.middleware.YokeRequest request, org.vertx.java.core.Handler next)

We also captured the com.jetdrone.vertx.yoke.middleware.YokeRequest object with accessor .path(). this gives you the URL which is called.

The interesting thing was that dynatrace captured already automatically the full purepath. We could see that the Purepath was correlated all the way through the aynchronous bus of Vertx. One remark here, everything was running on one JVM.

We defined 2 extra method sensors:

be.<customername>.common.cqrs.AbstractAddressableService$QueryHandlerHandler.handle(org.vertx.java.core.eventbus.Message event)

and

be.<customername>.common.cqrs.AbstractAddressableService$CommandHandlerHandler.handle(org.vertx.java.core.eventbus.Message event)

 On both methods we captured the argument with accessor: address(). This gives us the name of the service being called.

Couple of things which are not working or not yet found by instrumentation:

• They are using async mongo db client. Mongo DB statements are not detected. The synchronous MongoDB call was visible.
• Everything is running on the same JVM. No tests are done with message bus across different JVM's.
• HTTP return code not yet visible

Kind regards,

Chris