I can't set the level of monitoring in production. I enabled diagnotics in WebRole project(also with performance counters and Azure Storage connection). I check azure storage tables - data is written. How to enable changing monitoring level?
P.S. I user Azure SDK 2.5
There is a compatibility issue with SDK 2.5 that causes the verbose monitoring settings to be unavailable in the portal. To resolve this you should be able to add the following configuration setting to your csdef/cscfg and set it to a valid storage account:
<Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value="DefaultEndpointsProtocol=https;AccountName=diagstore;AccountKey=+Pgl4GVRy01UUy9uL4cFqsufI/79xsqBAHkNmYsDycfY8Qs5dZXzqgs8AZl1XsJWvGgEUsW/smz1DvswusCxjw==" />
SDK 2.6 will resolve this issue.
Related
Out of nowhere started seeing this error when opened function apps, Application is working though.
Unable to retrieve diagnostics and error information for your function app.
Encountered a StorageException while trying to fetch the diagnostic events.
Please make sure the connection string in the app setting "AzureWebJobsStorage" has the permissions to access Azure Table Storage
Storage account network access is set to "Enabled from selected virtual networks and IP addresses". Even with this settings there was no error before.
but now the above error message is gone only when changed to "Enabled from all networks".
Recently updated functionapp to dotnet 6.0 and v4 runtime even after, there was no error. Not sure if this has anything to do with this.
How do I fix for this?
This was caused by a platform level alert raised by a diagnostic component, and although it had no impact on the production workloads, the verbiage wasn't clear and the level misleading. The event has been disabled and you should no longer see this come up.
To expand, this error was reported by the control plane for the diagnostic component, which is meant to surface diagnostic events raised by production components to the portal, but not involved in any production workload flow and had no impact on the App's functionality.
We noticed the same issue in several of our functionapps. We also have configured the functionapp to be able to access the storage account via a subnet in a vnet, which worked fine until a few days ago. The functionapp itself is still working as intended, but it started showing this message a few days ago. As a test we did 'Enable from all networks' on the storage account, which resolved the warning message. I suspect there is some other service besides the functionapp which needs access to the storage account to read the functionapp diagnostic information. If I would know which service we could grant it access to the storage account without needing to 'Enable from all networks'
I raised a support ticket with Microsoft regarding this issue and was told that there seems to be a platform issue for App Services in West Europe region and they are currently investigating.
Where do I update the sink configuration for Azure Service Fabric
https://learn.microsoft.com/en-us/azure/monitoring-and-diagnostics/azure-diagnostics-configure-application-insights?
<SinksConfig>
<Sink name="ApplicationInsights">
<ApplicationInsights>{Insert InstrumentationKey}</ApplicationInsights>
<Channels>
<Channel logLevel="Error" name="MyTopDiagData" />
<Channel logLevel="Verbose" name="MyLogData" />
</Channels>
</Sink>
</SinksConfig>
These settings is set as part of the cluster creation, when you setup a cluster from azure portal, you have to provide Application Insights Key as part of the setup and it will create for your.
If you used ARM templates, you have to configure it on wadCfg section of your template.
Please take a look at this link to know more
Please take into account that these settings are targeted monitor and
log events from the cluster, if are planning to use these settings to
monitor you apps, I would recommend using EventFlow bundled in your
application. Because the cluster generally does not change as often as
your application does.
I want to enable azure diagnostics for my azure cloud service but I'm a little bit confused.
I read the article : https://learn.microsoft.com/en-us/azure/cloud-services/cloud-services-dotnet-diagnostics. I found also that I can enable azure diagnostics in the cloud service properties page by checking "Enable Diagnostics" in the Configuration tab of the cloud service. Also I can go more advanced by clicking the Configure button that shows up when you enable diagnostics.
The cause of my confusion is why in the article says you need to download the WadConfig.xsd file and configure everything and then upload an xml file while you can do the same thing (not sure the same thing) in the cloud service properties configuration?
It seems that Azure SDK 2.5 and later allow us to enable diagnostics and configure diagnostics configuration in UI by right-clicking on the Role and selecting Properties. But developers using Azure SDK 2.4 and previous versions can not manage diagnostic configuration in Visual Studio .
For detailed information, please read this blog.
I have Application Insights SKD on a ASP.NET application, but i can't see data on Azure Portal, I have followed the official documentation for troubleshoot and the connectivity with dc.services.visualstudio.com seems to be fine but i can't connect to f5.services.visualstudio.com, but f5.services.visualstudio.com seems not used anymore, I can't access it inside and outside of my network.
The account have access to Performance Logs too, and I uninstalled the SCOM Monitoring Agent to prevent problems, but still no data!
Check that assemblies are included in your project
Check you have last SDK version of Application Insights installed
Check ApplicationInsights.config file exists in the root of application and instrumentation key is presented
If you resolve InstrumentationKey from web.config or from another place, debug your application and ensure the InstrumentationKey is really resolved
Check your telemetries are collecting using the Visual Studio Diagnostics Hub (developer mode must be set to TRUE - by default)
Try to send more telemetries or change the flush interval to 0
First place where you can check your telemetries is Azure Portal - Diagnostic Search blade
Try to check quotas on Azure Portal
I was reading how we can detect request queueing problem in our Azure Service irrespective of level in our service at which it is queued.
http://blog.leansentry.com/2013/07/all-about-iis-asp-net-request-queues/
After reading the above mentioned article, I feel that setting up a monitoring on Http Service Request Queues\CurrentQueueSize performance counter is what I actually want. But now the question is how can I enable logging of this counter in Azure Diagnostics? I read over internet and didn't got much. Any idea?
When you create your project in Visual Studio you will see that you get a <Import moduleName="Diagnostics" /> in your ServiceDefinition.csdef file. This is what enables Windows Azure Diagnostics (WAD) in your deployment.
You will also see a diagnostics.wadcfg file in your Cloud Service project if you expand your Roles. In that wadcfg you can add any perf counters you want, and you will see some examples in there that you can use as a template. For the HTTP queue you would add something like:
<PerformanceCounterConfiguration counterSpecifier="\Memory\Available MBytes" sampleRate="PT3M" />
Once you do this then the perf counter will be in your storage account and you can query it using any standard storage tool, or one of the WAD tools such as Cerebrata, or you can configure Verbose monitoring from the management portal and then see the counter in the Monitor tab on the management portal.
Also note that Windows Azure Diagnostics 1.2 has just been released and is a good option if you haven't already enabled WAD 1.0 in your project. For more info see http://azure.microsoft.com/en-us/documentation/articles/cloud-services-dotnet-diagnostics/.