i try my first steps with Azure. I have upload a WebApp (Blazor WASM Serverhosted) on a Linux System. Now i want to see the logs. My application brokes on Azure on startup. Everything I have tried has not worked.
The logstream shows nothing.
The Monitoring/logs are disabled
I activate in Monitoring/App Service Logs the File System and go to FTP Folder and i don't find a log-folder or something like this
I hope for help to fix my App or Configuration on Azure
Still the issue can be available in github . You can achieve this by using below steps.
Steps provided here. And I am deployed in Linux app service
Now you can be able to view the logs in application insights
You can add/modify the custom logs as well by using the custom telemetry client.
Refer here for detailed information
Related
I'm trying to find a way to get dotnet-counters output from Azure App Services to either the Azure Portal (good enough for some trouble shooting) or some other console tool.
Does anyone know of a way to get the data, even when the app service is running across multiple app service plans? I was picturing maybe there is an app service extension (but no luck so far).
Eventually I'll want to automate this so I can get the data onto our monitoring system, but first baby steps.... just need something I can manually eyeball to help debug issues.
Anyone have any thoughts on how to do this?
Thanks
Ken
From offical doc, we can install dotnet-counters by cli command and download .exe directly.
As azure web app running in sandbox environment, so we can't add dotnet-counters to env, which means we can install it, but we can't use it.
So my solution is,
we can download .exe file directly.
After downloading finished, we can copy and paste it to wwwroot.
Then we can use it on scm site and azure portal.
On kudu site.
On azure portal.
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 am trying to deploy the basic-bot Microsoft Botbuilder sample application to azure.
I started by creating a new botbuilder node.js sample application through the Azure dashboard, and I was able to successfully follow the instructions here to download and redeploy the application.
I then attempted to copy over the deploy scripts and .env file from the downloaded sample application into the basic-bot application, and attempted to publish using the az bot publish command from the link above. This successfully deployed the basic-bot application, but the deployed application now returns 500 errors. Initially, the 500 errors were caused by the "botbuilder-ai" nodejs package not being installed. I installed this package manually through the Azure console, and this error went away. But the application continues throw 500 errors, without producing a stack trace, and I have not been able to determine why.
The only official documentation I have found that explains how to deploy the bot is specifically for C# and Visual Studio. Is there a way to deploy a bot to azure for a Node.js app using the azure CLI?
Thank you.
Is there a way to deploy a bot to azure for a Node.js app using the
azure CLI?
Yes there is. You can type az bot publish -h for all the options available to you when publishing a bot. Here are some tips about getting it to work:
You will need to log in to Azure with az login
Make sure you've set an active subscription. Type az account set -h for help. Use az account list to see your choices of subscriptions and az account show to see the current active subscription
Publishing can be easier if you set the resource group you're publishing to as your default. Unlike your active subscription, configured defaults don't reset when you log out. Use az configure to see your current defaults and az configure -h to see how to set a default resource group
If you publish and it says Not a valid azure publish directory. missing post deploy scripts then you'll need a PostDeployScripts folder in your bot folder
There are some instructions in the deploymentScripts folder that you might find helpful. Note that as an alternative to the Azure CLI, you can also publish from Visual Studio Code using the Azure App Service extension.
If you publish successfully and you're getting errors when you try to test in Web Chat, sometimes Azure needs a little nudging. When I checked my Channels blade it said Web Chat was encountering errors regarding missing files. I tried some troubleshooting steps and eventually got it to work without any real changes.
Try logging out of your Azure account in the online portal and then logging back in
Try running your code in the online code editor in the Build blade
Try publishing again
Regarding your specific situation of trying to repurpose the downloaded source code to deploy the basic-bot sample, there are a few things you need to know. The .bot file is very important as it contains information about all the services the bot uses, but basic-bot.bot contains none of the needed information. In addition to the deployment scripts and the .env file you will also need to copy over your .bot file. However, basic-bot's bot.js expects the .bot file to contain a LUIS service named "basic-bot-LUIS" so you need to go into the bot.js code and change the value of LUIS_CONFIGURATION to the name of the LUIS service in your .bot file ("BasicBotLuisApplication" if you downloaded the V4 Basic Bot NodeJS code and kept it the same). Make sure you can get the basic-bot sample to run locally before you try to publish it.
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.
I'm trying to learn to use the azure web app services to deploy a MEAN stack application.
I connected Web App deployments to a git repo and clicked deploy, which it appears to have done successfully.
When I load the webapp url in a browser, its a blank white screen.
How do I troubleshoot this scenario?
You should check if the correct ports are opened.
Good luck!
There are various steps for debugging Node.js web apps on Azure Web Apps here:
https://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-debug/
Start off by enabling logging in your IISNode.yml file by setting loggingEnabled: true and devErrorsEnabled: true and seeing what the logs say.
I usually use KUDU to debug Node.js application on Azure Web Site (currently named Web Apps). I doubted this might because the root directory was incorrect, i.e. your website should be started under ~/your_project/app but in Azure it was launched under ~/your_project.
Here is a doc for KUDU. http://blogs.msdn.com/b/benjaminperkins/archive/2014/03/24/using-kudu-with-windows-azure-web-sites.aspx