I have tried to get new relic to run inside my dnn 7 installation which runs in Azure web app.
I created a NewRelic account from the Azure portal and then I followed the directions here
The following APP SETTINGS were created in the configure tab of my web app:
NEWRELIC_LICENSEKEY : ****I used the one from my account*-*****
NEWRELIC_HOME: C:\Home\site\newrelic
COR_PROFILER_PATH: C:\Home\site\newrelic\NewRelic.Profiler.dll
COR_PROFILER: {71DA0A04-7777-4EC6-9643-7D28B46A8A41}
COR_ENABLE_PROFILING: 1
I then added the explicit app name to the web config, as instructed from the documentation link above, because I have the "Always On" enabled for my webapp
No data appeared even after restarting my web app numerous times.
So then I tried to set it up in the New Preview Azure Portal (am I the only one who hates the new portal, seems needlessly complicated.). I followed the instructions for the new portal here. This did not work either.
I manually uploaded the newrelic folder to the site root, and azure root folders and no success eighter. No logs are generated.
Can someone help me figure out what I am missing and why I can't get NewRelic to run in my DNN 7 azure web app.
Thanks in advance.
Jordan
Okay,
My web app was set to run 64 bit. The ddn site is not set up as a web project so I could not use NuGet to install a package. What I did was create a blank project and install the NewRelic package for 64 bit azure webapp
I than copied the files from that project and uploaded it into the site root of my web app, followed the instructions about manual install and restarted my website.
It now works.
Related
I've been following this tutorial on how to deploy a NodeJS app to Azure:
https://www.youtube.com/watch?v=RWdxkhajCg0&fbclid=IwAR10Q6x8PbqLDAZZzzMX9Nvp_jEGiN_Ts4V8XLJbzF6xreq6_MB_vsbIqx8
Firstly, I did everything exactly the same way as the author showed and it all worked. In the video, they're using Linux Web App Service. Since I have to get familiar with the Windows App Services (that's what I am required to learn and use for my job), I decided to deploy exactly same app to the Windows Web App service. However, instead of the home page, I only saw "You do not have permission to view this directory or page.".
I've already read bunch of solutions online, people suggest adding a web.config file, but it didn't help no matter what I added to that. The app is not supposed to limit any ip addresses/user groups as it's supposed to be a newly deployed app with no access restrictions (just as in the tutorial).
The only hint that I found out is that on Linux it works, on Windows it doesn't.
The app code is here:
https://github.com/Aitemir/MSP005
Because you uploaded the code to GitHub, my answer will help you very well. Jay's solution should also be effective, but he uses DevOps. If you are interested, you can also study.
Using Github to deploy web app will be very convenient.
Steps to solve my problem:
Download your source code and upload it to my Github.
Create a web app.
Use continuous deployment.
Delete .yml file. Delete all file in this folder.
View deployment status.
When you follow my way, you will successfully deploy your application. You can also put the generated web.config file in the current application in kudu, which should solve your problem.
I build a website with React and I deployed it on Azure. I build it and then deployed the build folder with vs code on Azure. The process is actually very easy using VS Code and the Azure extension. It is explained well here.
So far so good, everything worked fine. Now I needed to deploy the same app (the same build folder) but in another webApp. Basically, I needed to have separate versions of the app. So, I did the same things I did the first time (create webapp on Azure -> deploy with VS Code). However, I can't see my website when I go to the url. All I see is the default generated webapp, which is a dummy html page.
It looks something like this:
Hey, Node developers!
Your app service is up and running.
Time to take the next step and deploy your code.
I am seeking to understand this: I deployed the same build folder. I didn't change anything. I can't see my website (I thought it may take some time but I waited for nine hours now)
Things I've tried:
deploy again and again
restart the app on azure
stop and rerun the app on azure
go to the URL on incognito mode
I searched a lot and I've seen some answers that it can be about some path or file in the Azure configurations. However, I don't have anything in my configurations. Here are screenshots of my app configurations on Azure
here is my app configurations (when I go to configurations on Azure)
and these are the general configurations/settings
here is the deployment slots:
The message you are getting is the standard message when the app service is created but nothing is deployed.
Possible explainations are:
the app is being deployed to a different site
the app is being deployed to the same site but a different slot
the deployment is failing
your application is not listening on the port provided by the PORT environment variable
Recently I got into same issue,
Check you node version in package.json. I used this,
"engines": {
"node": "^12.16.3"
}
Azure web service was on Linux server. Startup commnand required in Azure General Settings -> Stack Settings
pm2 serve /home/site/wwwroot --no-daemon
You can also look at the log metrics after deploying or start the service. It will provide you info on the issue.
I'm new to deploying a web app to Azure (using Azure App Service). My app has about 6 web projects and we also use Umbraco CMS. When I build the web app in Visual Studio and point to any of our databases (dev, stage, etc.), the web site works locally (localhost)
When I try to publish the app to Azure or even test it locally (after "convert"), content is missing and all the links have the incorrect domain. I'm following MS docs to "Migrate and Publish a web app to Azure Cloud".
The first step in the MS docs is to right-click on the web app and select "Convert > Convert to Microsoft Azure". After this step I try to test the Web App created by this step. I point to the same databases as if i build locally (not using "convert"), content is missing and links have a different domain.
Is there a settings in the web.config or other file I need to do when building/deploying to Azure cloud service?
I have setup Sitecore 8.2 Update 3 as Azure App Service using Marketplace.
The setup completed and i got urls for cm and cd like
xxxxxx-cd.azurewebsites.net and
xxxxxx-cm.azurewebsites.net
But when I access these URLs I get this screen.
Also xxxxxx-cm.azurewebsites.net/sitecore gives page not found.
Am I missing anything?
According to your screen, the Azure App Service has been created, but there is nothing inside it. Seem like something went wrong and deployment script didn't deploy Sitecore's file to App Service. You can verify it using App Service Editor tool.
The reason why deployment went wrong could be this known issue: https://kb.sitecore.net/articles/755670.
With the new Azure Mobile App Services in Azure the mobile services apparently gains the same WebJob support as Websites have had for a while.
Following the article Deploy WebJobs using Visual Studio according to the section 'Enable automatic WebJobs deployment with a web project' we should be able to add a web job from a right click on the project. None of these options show up for my mobile service project in VS.
I can add a WebJob project to the solution manually, but this does not add the webjobs-list.json file to my mobile service project as the article suggests.
Does anyone know why the add web job context menu doesn't show when right-clicking on the mobile service project? Or the manual steps required to configure the project and appropriate webjobs-list.json file?
Update:
I have manually added the webjobs-list.json file to the main project by copying the format from another initial template project and adjusted the web job project path in it. Even deploying the mobile service to an azure web app doesn't pick up the web job.
It should work. I just created a new Mobile App, downloaded the quickstart, right-clicked the web project (appname-code), and was able to associate a webjob to the web project. Deployment worked as planned. Did you try that workflow? Did you try adding the webjob through the portal?