Question

We are using continues deployment from Visual stdio online to an Azure Website.

The deployment fails when we added new relic. "Exception Message: The file 'NewRelic.Profiler.3640.log' is in use."

If I Disable profiling, azure website>configure>app settings COR_ENABLE_PROFILING = 0 then the deployment works.

Is there some way to get this to work? Is it possible to add a step to the deployment process that sets COR_ENABLE_PROFILING = 0 and then afterward set COR_ENABLE_PROFILING = 1.

Was it helpful?

Solution 2

I was able to make the continues deployment work. If i copied the new relics folder out of the sites folder. And the change the new app config to use that one the site and deployment work. Not 100 % sure that new relic works but it seems to be doing alright

OTHER TIPS

This is a known limitation of New Relic's Azure Web Sites integration:

https://docs.newrelic.com/docs/dotnet/azure-web-sites#known_issues

I'm not sure if setting that Web Site app setting after deployment is possible or would cause the profiler to load. With other types of deployment for the New Relic .NET agent, IIS needs to be restarted for the profiler to load into the web worker process. The COR_ENABLE_PROFILING environment variable is just a flag that more or less gives the profiler permission to load. So I think the site would require a restart even if you could set the variable later.

Making it possible to use continuous deployment with New Relic and Azure Websites would require some coordinated effort between New Relic and Microsoft. You might file a feature request with both.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top