A bug had me pulling my hair this week

We are using Newrelic as a monitoring platform for our application.

It is a great tool but it had a limitation with how it would classify Reactor Netty transactions.

It would default to NettyDispatcher.

What that meant was when we look at API transactions, we would see all transactions NettyDispatcher instead of something like this:

• v1/TODO (POST)

• v1/TODO (GET)

So, we will not know which API is slow or erroring out.

Now, I wrote a custom code to get it working.

But getting the test to execute was a challenge.

The tests would abort due to JVM crashing.

Looking up the internet, I found the issue with the compatibility between Java 8, Reactor-netty library, and MacOS.

And yeah, I was pulling my hair on this.

I used 5 approaches mentioned in this video.

Did it work?

I had to use the last approach and guess what.

The issue was not resolved.

But I got an insight that will help me progress when I pick it up on Monday.

And what’s more, I will have another person looking at it over the weekend.

So yeah, the 5 steps work.

Go - watch the video!