Clever Geek Handbook

New relic on Azure Mobile Services with .Net backend

I would like to set up a new relic using the example of Azure Mobile Services with a .Net backend. The instructions I found apparently only apply to Azure Mobile Services with a JavaScript backend: http://azure.microsoft.com/en-us/documentation/articles/store-new-relic-mobile-services-monitor/

I tried the instructions for installing New Relic on Azure Cloud Services, hoping it would be similar to Azure Mobile Services, but unfortunately it didn't work. It showed the following error messages:

* Update project items newrelic.cmd, NewRelicAgent_x64_3.4.24.0.msi and NewRelicServerMonitor_x64_3.2.6.0.msi

* Update Windows Azure ServiceDefinition.csdef using the newrelic.cmd Startup task Unable to find the ServiceDefinition.csdef file in your solution, please make sure your solution contains an Azure deployment project and try again.

Updating Windows Azure ServiceConfiguration..cscfg files with a license key Could not find the ServiceConfiguration.cscfg files in your solution, please make sure your solution contains an Azure deployment project and try again.

* Update project .config file with NewRelic.AppName

* Full package installation

Azure Mobile Services does not use an Azure deployment project, so the required settings for New Relic cannot be saved there.

Now my question is, does anyone know how to get a new relic working for Azure Mobile Services with a .Net backend?

Thanks Jeffrey

+3


source to share


3 answers


Ok, I managed to get it working with the help of someone on the Azure Mobile Services team. The reason it doesn't work is a bug to be fixed, but at the same time it's easy to work there.

These are the steps to make it work:



  • Turn on Developer Analytics in the portal and select the new Relic add-on, then click Save.
  • Now if you look at "Application Settings" you should see "NEW_RELIC_LICENSE_KEY"
  • Rename "NEW_RELIC_LICENSE_KEY" to "NEWRELIC_LICENSEKEY" while maintaining the same value.

  • Add these additional settings to "Application Settings"

    and. COR_ENABLE_PROFILING = 1

    b. COR_PROFILER = {71DA0A04-7777-4EC6-9643-7D28B46A8A41}

    from. NEWRELIC_HOME = d: \ Home \ site \ wwwroot \ newrelic

    etc. COR_PROFILER_PATH = d: \ Home \ site \ wwwroot \ newrelic \ NewRelic.Profiler.dll

  • Click Save
  • Make sure you add the NewRelic.Azure.WebSites package to your project and publish

  • Refuse multiple requests to your service

    and. You can use the built-in test client right in the browser, for example: http://newrelictest.azure-mobile.net/help/Api/GET-tables-TodoItem

    b. For authentication, leave the username blank and paste the password into your app key. You can find your application key in the portal under "control keys".

    from. Click "try" and then send some GETs.

  • You can now start browsing your analytics through the New Relic portal.
+3


source


If deploying a .NET agent to Azure Mobile Services is possible, no one has documented it. Microsoft made it possible to deploy the Node.js agent in mobile services; they will have to do the same for the .NET agent. Your best way is to contact Microsoft Azure support directly.

Please post here if they have a solution. It would be great to include this on both stackoverflow and the New Relic Community Forums .



Regards, Kyle

+2


source


You can use NewRelic with a .NET backend, but you will need to do some manual work as the built-in support is not ready yet. Here are the steps you'll need (I'll refer to the tutorial to add NewRelic monitoring to the node.js backend , so as not to overwrite what's already there):

  • Sign up for a new relic using the Azure Store: same steps as in the corresponding section of the node.js tutorial
  • In the mobile service project on VS, install the "New Relic for Windows Azure Websites (x86)" NuGet package - ( NewRelic.Azure.WebSites )
  • Publish the project to Azure
  • Enable NewRelic Developer Analytics for Mobile Service:
    • Start at the relevant section in the node.js tutorial
    • Now go to your mobile service app settings and add the following 5 keys:
      • COR_ENABLE_PROFILING, value: 1

      • COR_PROFILER, value: {71DA0A04-7777-4EC6-9643-7D28B46A8A41}

      • NEWRELIC_HOME, value: d:\Home\site\wwwroot\newrelic

      • COR_PROFILER_PATH, value: d:\Home\site\wwwroot\newrelic\NewRelic.Profiler.dll

      • NEWRELIC_LICENSEKEY, value: <same values ​​of NEW_RELIC_LICENSE_KEY parameter>
  • Build traffic for your mobile service. At this point, you should be able to track maintenance in the NewRelic dashboard (same steps as the corresponding section in the node.js tutorial )

Please note that the additional steps listed below (adding custom application settings) are a temporary workaround while the product does not complete the integration between the .NET backend and developer analytics.

+1


source






More articles:


All Articles