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

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…