Episode 121: New Relic

Download this episode

Download Video

Download captions

Download Captions

Description

In this episode Nick Harris and James Baker are joined by Nick Floyd, an Agent Developer at New Relic.  In this episode, Nick will walk through:

  • Signing up for a free New Relic subscription in the Windows Azure Portal
  • Connect the subscription to a new web site in Azure
  • Add the New Relic NuGet package to a web site in Visual Studio
  • Navigate to the New Relic portal from the Windows Azure Portal
  • View different performance metrics for the web site
  • View performance metrics on a site and it's connected SQL Database

Like Cloud Cover on Facebook!




 

Embed

Format

Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image
      John Woakes

      I tried to get this working but after I clicked Add-ons, New, Store, I got this message;

      The subscriptions you selected are not currently available for purchase in your region. Additionally, the Store is not available to users who have an Enterprise Agreement...

      Is there a way for me to try out New Relic? This error message does not make sense to me.

    • User profile image
      deef

      Got the same error trying to add new relic as add-on in the azure portal.
      But I'm sure you can go to newrelic.com, get an account there and add your license key to the web.config.

      We've been using new relic (pro) for a year now, it's really amazing.

    • User profile image
      nickfloyd

      Hey John,

      Deef is spot on.  You can signup @ http://newrelic.com/azure, after that you just click on your account name in the upper right corner, choose "account settings" and you'll find your license key on the right.

      Then in the azure portal, under your WebSite >> Configuration >> Developer Analytics choose "custom" | New Relic as the provider and then paste your license key in the provider key field and "save"

      A little more footwork than if you were able to go through the store but it will net you the same result.

    • User profile image
      Richard Nunez

      All:

      We continue to improve the user experience with Azure engineering. Should you have any issues through the store at all, please visit us at www.newrelic.com/azure. Also, feel free to shoot us a note to our Partner Response Center, prc@newrelic.com. We'll make sure you get all the support you need to get up and running with New Relic.

      Rich

    • User profile image
      RhysC

      Just to let anyone out there that cares - there is a small C# query wrapper api for New Relic at https://github.com/rhysc/linqtonewrelic
      Fell free to add or extend it.

      Cheers guys

      Rhys

    • User profile image
      Will Merydith

      John and deef, at this time the Store does not support EA accounts (billing). Store is still in preview, and EA support is on our roadmap.

    • User profile image
      Sandeep Sachan

      We are using New Relic since couple of month. When I'm using dashboard I can see a method called application begin request takes a lot of our cpu and tones of weight lifting.. we want to trace it even further to go and check which part of our code is really causing this issue.

      And it happen only when we deploy the app on azure instance and only at app-pool warm-up process for the application. I understand we can do use other custom file based logger to write individual timestamp. -Just wanted to know if new-relic can help up to investigate?

    • User profile image
      nickfloyd

      Hey Sandeep,

      The BeginRequest slowness is sometimes related to thread agility or thread locking issues. Given that it only happens for you when you deploy / on warm it's most likely related to the startup of the ASP.NET process and JIT compilation.

      The New Relic .NET Agent works by leveraging the CLR profiling API. When a profiler is attached, the CLR will JIT compile all methods in the .NET Framework when they are first used. This is different from normal runs where precompiled versions of the .NET Framework libraries are used in order to optimize application startup times. This cost is is something that will generally occur once per process, plus a little bit per application domain (Web Application for IIS). As the process is spinning up for the first time much of the JIT compilation for the application will probably happen at that time.

      Normal warm up delays, though, is one of the reasons Microsoft introduced Application initialization in IIS. Since you cannot configure native modules (like Application Initialization) on Azure Web Sites they have provided a way for us to be able to gain some of the benefits "warming" through the always on configuration in Azure Websites.

      http://weblogs.asp.net/scottgu/archive/2014/01/16/windows-azure-staging-publishing-support-for-web-sites-monitoring-improvements-hyper-v-recovery-manager-ga-and-pci-compliance.aspx

      Other than that you can always use the normal set of things to help speed up the loading of your Web Application (regardless of it being an Azure Web Site like): enabling compression, enabling caching, minify your JavaScript and CSS and so on.

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.