Skip to main content

Azure Application Insights– Collect Performance counters data

One of the features you get out-of-the-box when using Application Insights is the ability to collect performance counter data. This allows you to track statistics like CPU, memory and disk usage.

In ASP.NET Core the following counters are collected by default:

  • % Process\Processor Time
  • % Process\Processor Time Normalized
  • Memory\Available Bytes
  • Process\Private Bytes
  • Process\IO Data Bytes/sec
  • Processor(_Total)\% Processor Time

When the performance counters are collected correctly, you can use them as one of the available metrics in Application Insights:

Troubleshooting performance counters collection

But what if no data is returned?

First thing you should check, if you have a related log message. Therefore run the following KQL query inside the Logs section:

traces
| where message startswith "AI: Error collecting"
| limit 10


In my case it returned the following error message:

AI: Error collecting 6 of the configured performance counters. Please check the configuration.
Counter \Process(??APP_WIN32_PROC??)\% Processor Time: Access to the registry key 'Global' is denied.
Counter \Process(??APP_WIN32_PROC??)\% Processor Time Normalized: Access to the registry key 'Global' is denied.
Counter \Process(??APP_WIN32_PROC??)\Private Bytes: Access to the registry key 'Global' is denied.
Counter \Memory\Available Bytes: Failed to register performance counter. Category: Memory, counter: Available Bytes, instance: .
Counter \Process(??APP_WIN32_PROC??)\IO Data Bytes/sec: Access to the registry key 'Global' is denied.
Counter \Processor(_Total)\% Processor Time: Failed to register performance counter. Category: Processor, counter: % Processor Time, instance: _Total.

This error message rang a bel and a search on my blog returned the following post from 2019:

https://bartwullems.blogspot.com/2019/09/access-to-registry-key-global-is-denied.html

To solve the issue, we have to add the Application Pool user(use the following name: IIS AppPool\<applicationpool name>) to both the Performance Monitor users and Performance Log Users group.  After doing that, the error should disappear.

Remark: Don’t forget to restart the application pool after adding the user

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more