Skip to main content

Performance Counter Setup on Windows Azure

Cand avem o aplicatie in cloud avem nevoie de a monitoriza diferiti parametrii. Acest lucru il facem asa cum il facem si pe un server normal folosindune de performance counter.
Intrebarea ar putea sa fie usor diferita: Ce facem cu aceste valori odata ce le avem?
Daca intram remote pe masina, puten sa ne folosim perfmon.exe pentru a monitoriza toti acest parametrii. Dar daca vrem mai mult de atata, daca vrem ca aceste valori sa le putem accesa remote sau sa le persistam in Azure Storage.
In ajutor ne-a venit in ajutor Microsoft si ne-a oferit DiagnosticMonitor pentru Azure. Acesta poate sa fie configurat destul de usor in momentul in care aplicatia porneste si ne va permite sa scriem orice valoare in Azure Tables. In exemplul de mai jos o sa prezint cum se configureaza pentru a putea vedea load-ul la procesor:
var config = DiagnosticMonitor.GetDefaultInitialConfiguration();
config.PerformanceCounters.ScheduledTransferPeriod = TimeSpan.FromMinutes(30);
config.PerformanceCounters.DataSources.Add
new PerformanceCounterConfiguration() {
CounterSpecifier = @"\Processor(_Total)\% Processor Time",
SampleRate = TimeSpan.FromSeconds(30)
};
Deoarece fiecare tranzactie se contorizeaza la sfarsit de luna, am setat ca flush-ul la date sa se faca odata la 30 de minute. Odata ce am facut aceasta configurare ajunge sa pornim diagnosticarea pentru noua configuratie:
DiagnosticMonitor.Start("Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString", config);
Am vazut ca la unele persoane nu este foarte clar ce valoare reprezinta "\Processor(_Total)\% Processor Time". Aceasta reprezinta CPU usage in momentul in care s-a facut requestul. Valoare este media la CPU usage pentru toate procesoarele masinii noastre.
Aceasta setare este nevoie sa o adaugati in entry point-ul aplicatiei voastre din cloud. Clasa care reprezinta entry-point-ul pentru o aplicatie in cloud are ca si clasa de baza RoleEntryPoint.
Mai jos gasiti o implementare cap coada a unui performance counter.
public class WebRole : RoleEntryPoint
{
public override bool OnStart()
{
var config = DiagnosticMonitor.GetDefaultInitialConfiguration();
config.OverallQuotaInMB = 4080;
config.ConfigurationChangePollInterval = TimeSpan.FromHours(1);
config.PerformanceCounters.BufferQuotaInMB = 128;
config.PerformanceCounters.ScheduledTransferPeriod = TimeSpan.FromSeconds(60);

config.PerformanceCounters.DataSources.
Add(new PerformanceCounterConfiguration
{
CounterSpecifier = @"\Processor(_Total)\% Processor Time",
SampleRate = TimeSpan.FromSeconds(30)
});

DiagnosticMonitor.Start("Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString", config);

return true;
}
}
Odata ce am facut aceste configurari si am facut un deploy (sau am rulat aplicatia local) o sa puteti observa ca apare o noua table in Windows Azure Tables. Aceasta poata numele de "WADPerformanceCountersTable" si o sa contina toate valorile de la toti performance counters pe care ii monitorizati. In acest tabel o sa gasiti toate datele despre performance counters pe care voi ii monitorizati.
Pentru a putea vizualiza aceste valori mai usor, va recomand sa folositi Cloud Monitoring Studio. Este un tool gratis de pe codeplex care iti permite sa vizualizezi toate datele sub forma unui grafic.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too