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

Update on New Relic .NET Core support



You’ve heard New Relic assure you that we’ll provide support for .NET Core but we’ve been light on details resulting in our community of customers feeling frustrated about both the lack of support for .NET Core and lack of updates.

First of all, we get why .NET Core is important to you. .NET Core is an exciting change in the Microsoft ecosystem that benefits Microsoft developers in ways that developers in other language ecosystems have enjoyed for years. We know you’re excited to run applications on Linux and take advantage of both the ease of use and the incredible performance improvements available when using .NET Core.

We’ve been working with .NET Core for a while now and have seen how it’s matured over the last several months: .NET Standard 2.0 is coming out, project structures are solidifying, API availability is hardening, developer toolset is growing and, most importantly, we’re seeing the Microsoft developer community embrace .NET Core as it’s reached maturity.

New Relic is committed to supporting .NET Core and I’d like to share the high level plan we’re executing behind the scenes to bring .NET Core support to you.

Phase 1 (already in progress)

First up, we’re working to prepare the New Relic .NET agent, which includes changing the build infrastructure, implementing new performance and functional test coverage, and removing pre-async code and legacy dependencies, among other projects to ensure .NET Core and .NET Framework are both adequately supported. With this phase, we’re setting up the .NET agent for faster innovation.

Phase 2 - Full ASP.NET Core Support for the Agent running in Windows

During this phase, we will build support for profiling an ASP.NET Core application using the .NET agent on a Windows server. This will be our first generally available release of the New Relic .NET agent that supports .NET Core applications.

Phase 3 - Basic ASP.NET Core Support for the Agent running in Linux

With this phase, we will build support for running the .NET agent on an ASP.NET Core application on Linux.

Not included in this phase is profiler integration since the CLR profiler APIs for the Linux platform remain unverified. However, we believe in providing as much functionality as we can, when we can, so we plan to release the Linux support we do have if we end up getting blocked by this.

Phase 4 - Implement Profiler Support for .NET Core on Linux

New Relic plans to publish our findings from our Linux CLR profiler API tests to the community. For all the CLR profiler API functionality that we validate, we intend to add profiling support for Linux into the .NET agent. This will give users the ability to profile an ASP.NET Core application using the .NET agent on a Linux server.

How to get involved

We hope to learn a lot from our customer community as we progress through each of these phases. Tell us what your environment looks like and let us know if you’re interested in participating in an early access program by completing this survey.

Take the .NET Core Support Survey!

Your input will help shape the direction we move in!

Here’s something Legal makes me say every time I talk about things that we’re in the process of building but haven’t yet shipped:

This post contains “forward-looking” statements, as that term is defined under the federal securities laws, including but not limited to statements regarding the .NET Core Agent as well as potential benefits derived therefrom. The achievement or success of the matters covered by such forward-looking statements are based on New Relic’s current assumptions, expectations, and beliefs and are subject to substantial risks, uncertainties, assumptions, and changes in circumstances that may cause New Relic’s actual results, performance, or achievements to differ materially from those expressed or implied in any forward-looking statement. Further information on factors that could affect New Relic’s financial and other results and the forward-looking statements in this press post is included in the filings New Relic makes with the SEC from time to time, including in New Relic’s most recent Form 10-Q, particularly under the captions “Risk Factors” and “Management’s Discussion and Analysis of Financial Condition and Results of Operations.” Copies of these documents may be obtained by visiting New Relic’s Investor Relations website at or the SEC’s website at New Relic assumes no obligation and does not intend to update these forward-looking statements, except as required by law.

Feature Idea: .NET CORE / ASP.NET 5 (vNEXT)
After configuration .NET agent not getting data from site
NewRelic not capturing custom-instrumented async transactions

That’s a good start, but it’s hard to plan around without some indication of how long you expect each phase to take. Are we talking 3 months? 6 months? an entire year?

Also have to say I’m surprised that you’re trying to merge .Net Core support into the existing .Net Agent instead of forging ahead with a separate, lightweight, dedicated .Net Core agent (or even better, a profiler that can be installed into the app using NuGet rather than requiring Agent installation on the target server).


Disappointed to say the least that no .Net Core support is available yet and that the above verbiage still seems to suggest its a ways off. We’re looking to use .Net core on Ubuntu 16.04 containers running under Mesos/Marathon or Kubernetes and the kestrel stand alone http service would be awesome to be able to use. (using our own load balancer/content switcher or slb’s on cloud)


Yes @kirsty_luke and @bmiller — as you may have gathered from hanging out in this community, we do not share dates regarding our upcoming roadmap. Yes, that is frustrating and disappointing at times like this. You are both justified and I am glad you can candidly share your feelings.

What would be really productive is if you let it all out in our:

.NET Core Support Survey

That way we here at New Relic can use the constructive suggestions and input you have for us to move this forward as quickly as possible.

Thanks for being part of the process. Your voice is more important than you know. :blush:


This information is useful as a “nice to know that you are at least doing something and that you have a roadmap” However, it falls short of being really useful because without dates (even rough dates) these plans mean nothing. “The road to hell is paved with good intentions” as the saying goes.
The disappointment continues…


@rchung - Sorry you’re disappointed about lack of a date. My intention with transparently telling you the phases is so you can see our progress via release notes. I get your perspective: words are wind. There’s nothing we can do but stay heads down on getting support out for .NET Core to earn your business.


Will New Relic support ASP.NET Core before it supports .NET Core? We have ASP.NET Core running on the Desktop CLR. I don’t see why New Relic couldn’t instrument that easily.


This announcement would have been welcome a year ago. Given the imminent RTM of Visual Studio 2017, we should be seeing a release candidate for Phase 2 - not learning that it hasn’t even been started.


What about Nano Server? Will New Relic be installable there? Nano Server only supports .NET Core, so you would need to rethink bundling .NET Core and .NET Framework support together.


I understand your reluctance to provide dates. However surely you can say “Not be before date X”.

For example, “we don’t expect Phase 2 to be released before July 2017”. It makes no commitment that if broken would result in people being disapointed. But it does give your customers more information on which to plan.


We have .NET Core applications that are pending instrumentation. No venting here, just adding to the list of apps waiting for support.


Hello guys,
do you have any information about the .Net Agent Api on the .NET Core 1.1?
We have to implement on the linux machine
Thank you


Guys, do you really will wait release of .Net Core 2.0? By MS plans it is Q3’17, more and more enterprise .net platforms shifting to .Net Core especially after VS’2017 release, so now we all should wait NR to support our monitoring and custom events?


Yup - you are going to have to wait, @h0use! We can only ask for your patience at this point as we hustle to make the best darn option on the market for your .NET Core monitoring.

These things go a lot faster with your input so please make sure you fill out this survey. << You too, @a.vasapollo! Thanks!


any more update on this being released -


Bump. Any updates on this front?


I just wanted to update this thread that we’re now opening up the Beta for the .NET Core 2.0 Agent on Windows. You can read more about it here.


I was wondering if there is any other updates on a potential release date for .NET Core NewRelic agent on Linux. Our company uses NewRelic for all our other services and I need to know whether or not I need to find an alternative APM for our .NET Core services.


thanks for the information. i’m definitely going to read that later as now my wife wanna take me a cialis and go with her so i don’t have the time. but i would so much rather learn here guys. thanks. also, would you mind if i am going to have some questions for you? thanks!


We have the .NET Core 2.0 Agent for Linux available now as an Open Beta. There are two forms to get onto the Open Beta, one company wide form that your company only needs to use once to be approved for using New Relic pre-releases and a second to get onto the open beta (Update 10/24: Thank you for your interest in the .NET Core Beta, we have reached the maximum capacity and our team is now processing the feedback we’ve received in final preparation for the GA). We’ve gotten some great feedback so far from our Beta customers and are working hard to build and include some of the feedback into our agent before the GA of our Core 2.0 capabilities.

NewRelic insights / APM on .net core apps deployed in Cloud Foundry