I am intending to enable logging in my Azure app. I am following the instructions by Microsoft on here, where they state to go to my app and select App service logs, but I see no such option for my app. This resource has the same instruction but I don't have that option. I am running on the Basic configuration for the app (the cheapest option), could that be the issue?
This is all I have under Monitoring (see image below)
What am I missing?
Which region are you running your app service on?
I just tried with Basic(B1) app service and I was able to configure app service logs
Seems like I had to upgrade to a minimum of Standard tier configuration to get the option to set up App Service Logs. It is Unfortunately about triple the cost of the Basic tier.
Related
I am currently deploying a C# console app as a Continuous Azure Web Job to an Azure App Service and I am using the Azure Web Jobs SDK 3.X(https://learn.microsoft.com/en-us/azure/app-service/webjobs-sdk-how-to).
The Web Job successfully deploys to the Azure App Service but the status of the Web Job is "Pending Restart". When I check the logs, the error I see is that a configuration value is being read in as NULL. I am setting this value in the App Service's configuration/Application Settings page but it seems my Web Job is unable to read it. Do these settings need to be set during deploy? Or do I need to be setting these configuration values in a different location?
My issue was that my app thought that my environment was Develop and it was looking for the appsettings.Development.json file. Once I corrected that issue, it looks like I am reading in my app settings correctly.
Azure PremiumV2 app service plans lose the ability to attach remote debuggers over Standard app service plans:
Remote debugging: When you scale your app to PremiumV2, you will no longer be able to use remote debugging for your apps. If you scale your App Service plan to a lower tier, you will be able to use remote debug again.
https://azure.github.io/AppService/2020/03/23/PremiumV2-support-for-older-deployments.html
I've looked at the documentation for the new PremiumV3 app service tier, and can find no reference one way or another to remote debugging.
https://learn.microsoft.com/en-us/azure/app-service/overview-hosting-plans
https://learn.microsoft.com/en-us/azure/app-service/app-service-configure-premium-tier
Do PremiumV3 allow for the attachment of remote debuggers, and is there any indication of the long term strategy around this feature?
I span up a .NET 6 minimal API project, uploaded to a app service, changed the app service plan level, and where possible, attached a remote debugger from Visual Studio 2022 to observe a GET request.
I've tested each tier, and have the following results:
Tier
Remote Debugger Support
F1
YES
D1
YES
B1
YES
S1
YES
P1
YES
P1V2
NO
P1V3
NO
I have created an App service with V3 plan.
Deployed WebApp to the App service.
Tried to Attach debugger from Visual Studio,It changed the settings of Remote Debugging to On but unable to hit the break point.
Even there is an option of Remote Debugging in Azure Portal,the debugger is not attached to it.
I have created an azure web service app used for testing purposes and run into a .Net / http issue (500.30). Ive looked into a lot of troubleshooting but nothing has worked or pointed me in the right direction.
It seems to get more info on the issue, I can use the stdout logs in the Azure app service through Kudu. This has been configured this and the files it creates are blank? Has anyone encountered this before?
What have I did, I set it up in the web.config file setting the stdlog to true but this creates the files with no info. I then removed the inprocess=hosting section as I read this fixed it for others but no joy.
Any pointers in the right direction would be appreciated
HTTP Error 500.30, The log file is created but empty - This kind of scenario is trapped by the SDK when publishing a self-contained app.
There is a term called RID (Runtime Identifier) used to identify target platforms where a .NET Core application runs.
If the RID doesn't match the platform target then the SDK produces the above kind of errors.
For example, win10-x64 RID with <PlatformTarget>x86</PlatformTarget> in the project file.
Troubleshooting steps:
<PlatformTarget>x86</PlatformTarget> enables the IIS app pool for 32-bit apps in an x86 framework-dependent deployment and set Enable 32-bit Apps to True from the app pool's Advanced Settings of IIS Manager.
500.30 is In-Process Startup Failure as it's cause can be usually determined from entries in the Application Event Log and the ASP .NET Core Module stdout log.
The app is misconfigured due to targeting a version of the ASP .NET Core shared framework that isn't present. Check which versions of the ASP .NET Core Shared framework are installed on the target machine.
If you're using Azure Key Vault, check the policies in the targeted Key Vault to ensure that the correct permissions are granted.
Also, please visit this Thread related to logging not working fix.
And Application Insights should be enabled to get the log files in the Storage account.
You can stream the logs from the portal or using CLI:
az webapp log tail --name appname --resource-group myResourceGroup
Use this reference to get the logs using the simple queries.
You need to enable application logging first.
Click on the App Service logs menu
In Application logging, select File System
In Quota (MB), specify the disk quota for the application logs. In Retention Period (Days), set the number of days the logs should be retained.
Save
You can stream the logs from the portal or by using the CLI
az webapp log tail --name appname --resource-group myResourceGroup
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
When I create a web app for containers, then the deployment options are disabled in the Azure portal. The option is enabled if I create a regular web app and another type of resources. For web app for containers, the options was working fine till a few days back and I have no idea what triggered it to become disabled. My subscription is active and clearing browser cache, switching browsers, working with different container images, deleting and recreating resource groups, and login/logout do not help. Any suggestions?
The "Enable Deployment Options within Web App for Containers in the portal" feature was requested on feedback.azure.com and declined.
Q. Currently "Deployment Options" is only available for Web App for Windows/Linux. It would be nice if this was enabled for Web App for Containers...so I lost the simple ability to deploy from BitBucket.
A. The App Service team responded: We are declining this request since we actually discourage customers to deploy this way and recommend deployment with Container Push. That being said, there is nothing stopping you from configuring this through CLI.
To do this from the CLI, you could use this command:
az webapp deployment source config -n appname -g resourcegroupname --repo-url <gitrepo url> --branch <branch>
See Manage Web App for Containers using Azure CLI for more details.
I have created Azure Web App which OS is Docker and reproduced your issue.
From the screenshot , we can find the issue may caused by App Service Plan. I have tried to use all tiers of plan, including Isolated, but the issue is still existing. Also, for regular web app, not have the issue.
I find some updates on Azure App Service. I am not sure if the issue was caused by the updates, I recommend you to contact App Service Support Team for help.
The customer support team resolved the problem and cited "platform issue" as the cause of the problem. Now deployment options for container web apps is enabled and working again.