Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

Feature Idea: Add Support for NServiceBus Version 6

feature-idea
nservicebus
rfb

#21

@khansen An addition to the above statement. You could try to verify my doubt by making one of your command handlers synchronous. Move all your code in the handle method into an async inner method and then call the async inner method with .GetAwaiter().GetResult() in the handle method to see how this changes the reported time.


#22

@hross We managed to get in touch with all our customers that complained about this issue. Seems we have a working workaround, but we’d rather have a proper fix in NewRelic. How could we raise that with you?
It’s not really a new feature, rather an update to what you already have. We can share with you the solutions we have if needed.

Should I raise a support ticket with you? Or what else could I do?


#23

Hi there @weronika.labaj -

Thanks for the continued updates. At this time, we’ve put in the request with the engineering team to support this in the .NET agent without workarounds. So they know, but I can’t promise that it’s coming, or that it’s coming in any specific time frame.

If you do have code that you think would be helpful for us to see and you can share it publicly, please feel free to post it here, and we’ll add it to the notes about this request. Otherwise, you can DM me and I can do the same thing.

Best,
Holly


#24

@daniel.marbach I got in touch with NR support. Their first suggestion was to add a name attribute to the tracerFactory tags in https://github.com/danielmarbach/NewRelic.Providers.Wrapper.NServiceBusV6/blob/master/NewRelic.Providers.Wrapper.NServiceBusV6/NewRelic.Providers.Wrapper.NServiceBusV6.Instrumentation.xml as follows:

<tracerFactory name="NewRelic.Providers.Wrapper.CustomInstrumentationAsync.DefaultWrapperAsync">

However, rather than alleviating the transaction time issue, this caused reporting to go blank again (no transactions recorded).

This is the latest reply from NR support:

It seems like the call is instrumented correctly when viewed as an external but not as part of a transaction. I am wondering if we are essentially tracking/recording it twice but with different wrappers/logic. It almost sounds like it is not getting included at all in the transaction.
Also, clicking on the Transactions tab doesn’t show any transactions. However when I click on a transaction from the Overview page I do see the transactions. Not sure if it is related but it the behavior is strange. This is similar to a known issue but it has been determined that they are different.
I’m guessing that the use of NewRelic.Providers.Wrapper.CustomInstrumentationAsync.DefaultWrapperAsync is subverting the generation of the transaction which the hacked wrapper is trying to generate.
Again, there isn’t much else we can so with this since we don’t own it but if you work with other engineers and figure it out, feel free to let us know the solution.


#25

@khansen I’m not an expert in NewRelic. According to my understanding adding that tracer factory would basically unhook the custom wrapper that I wrote and replace it with the DefaultWrapperAsync which has no knowledge of the transaction and the specific segment you want to intercept. That’s why you see nothing.

I updated the sample https://github.com/danielmarbach/NewRelic.Providers.Wrapper.NServiceBusV6/commit/fa5a9b502640e2d89d79ddabcc8204ed29045459 I tested it and I see data but I don’t think it is accurate enough yet. I will try to reach out to support of NewRelic and see if I can get someone on the phone.


#26

Hi everyone,

First off thanks to @daniel.marbach and @Jake.Stevenson for looking into this. Is there any more news about this?

@daniel.marbach, I looked into using your solution. This requires several New Relic dll’s, amongst which ‘NewRelic.SystemExtensions.dll’. This file, however, is not present in my New Relic agent folder.

Kind regards,
Rob Vanmeert


#27

Hi Rob,

I tried to contact NewRelic several times over the last few weeks. Linds promised me to come back on this but it seems the ball has been dropped. So now news yet.

About the assemblies that you need should be under

C:\Program Files\New Relic.NET Agent and
C:\Program Files\New Relic.NET Agent\Extensions

I have to stress again here that I don’t recommend this because I have no idea whether this is a violation of licenses or not. I’m also not working for NewRelic. I came up with this “hack” to get customers unstucked. Use it at your own risk. Hopefully, at one point NewRelic will get active on this issue and get all the people in this thread unstucked.

Daniel


#28

Another incredibly frustrated New Relic and NServiceBus customer here. We’ve migrated half of our MicroServices to NSB6 and paused the migration because we are now blind in New Relic. I am strongly encouraging New Relic engineering to take the Olive Branch from Particular Engineering (offered earlier in this thread). Let’s get this fixed ASAP.


#29

We implemented a number of microservices based on NServiceBus Version 6 and I would also really like to see full-featured New Relic support for this version (and, hopefully, for the upcoming Version 7 as well).

Dmitry


#30

Throwing my hat in the ring here too. This issue is 100% holding us up from upgrading to NServiceBus 6 which, among other things, would allows us to properly leverage async/await. Please, at the very least, an update from New Relic would be appreciated.


#31

The value we get from NewRelic has gone down considerably as we’ve transitioned our microservices to the latest NServiceBus release, we now have very little insight into the services that have made the jump. NServiceBus 7 is coming down the pike as well and we’re very concerned that we’re not going to be able to recreate the level of monitoring we once had again. I’m not sure if there are technical challenges that are preventing NewRelic from supporting this class of enterprise software, but some communication is warranted from the NR team so we understand what our options will be moving forward. This is a very serious concern for us going forward, so we hope NR will begin to communicate again about this feature very soon.


#32

Hi @bconneen, @DmitryZinchenko, @mikesigs and @scott.wilson

I’m Daniel from Particular. I tried to reach out again to Linds and offered our help. Fingers crossed that we might get an answer this time. I’ll keep you posted.

In the meantime feel free to join https://discuss.particular.net/ if you want to discuss further details.

Regards
Daniel


#33

@daniel.marbach - thanks for offering to help. I’m a new Product Manager at New Relic and so I’m always happy to hear about the needs of our customers. Right now the focus of the .NET agent team here is majorly on .NET core 2.0 but we do recognize the value that NServiceBus provides and so, we will be prioritizing this in the roadmap for the .NET agent and will reach out to you to see how we can leverage what you have built.


#34

Hi @bconneen, @DmitryZinchenko, @mikesigs and @scott.wilson

We created a sample that shows how to integrate the new NServiceBus.Metrics package with NewRelic. You can find it over here https://docs.particular.net/samples/logging/new-relic/

It uses custom metrics so it might not behave exactly as the previous v5 plugin but at least it should give you good data indicating what is going on in your system. I suggest to use the Metrics v2 version with v6 since this one supports retries and also puts the message type name into the generated metric.

A sample dashboard with Insights

I hope this gets everyone in this thread unstuck.

Regards
Daniel


#35

Thanks so much for sharing @daniel.marbach. We love it when you share with your fellow friends!


#36

Any Update? We’re also interested in full support for NSB6 in NewRelic and have lost a lot of New Relic value after our upgrade.


#37

Sorry to hear that, @gblakely!

Be sure to add your vote in the poll above and I will pass your request on to our Product Managers. :thumbsup: