Skip to main content

Should I use Azure Monitoring or Azure Service Health?

By
In this post, we will try to respond to a simple question:

Should I use Azure Monitoring or Azure Service Health?

It is important to emphasise that there is no overlap of the features that each service is offering.

  1. Azure Service Health: inform us about outages or planned maintenance on Azure Services that we are using
  2. Azure Monitoring: inform us about how our application performs and provides us with information to identify and track issues inside our app.

In a standard scenario, we need both services during the operation phases. One service is providing us with information related to the current health status of Azure Services that we are using. The other one offers us insights related to our application insights.

Azure Monitoring
Using Azure Monitoring, we can collect, analyse and react based on information that we collect from Azure Services, applications or any other systems that are involved. The no. of data sources supported by Azure Monitoring is vast and includes:
  • Application
  • Operation System
  • Azure Subscription
  • Azure Resources
  • Azure Tenant
  • On-premises data sources
  • Custom sources
One of the most significant benefits of Azure Monitoring is the capability to aggregate metrics, logs and audit from multiple sources and consolidate them in one central location. From it, we can run queries and drill down inside issues.
Even if Azure Monitoring has a powerful dashboard, we should remember that it is well integrated with other systems. In this way, Azure Monitoring can become easilty a data source for PowerBI or for Workbooks.

Azure Health
It's the source of truth when you want to know if a specific Azure Service that you are using has health issues or when planned maintenance takes place. When one of Azure Services that you are using has health problems, the Azure Health will notify you.
You might say that this is an overlap with Azure Status dashboard, where you can see the current status of all Azure Services cross the globe. The difference is that inside Azure Health you see the outages, health issues and maintenance events that are affecting you.

The power of alerts
Both services that were covered in this post support alert notification. Using alerts we can create the notification system that would allow our operation team to get notifications related to health issues of Azure Services that we are using or issues of our application and system automatically.
Additional to this, notifications can trigger auto-scaling actions or custom flows that can execute disaster recovery or any other actions.

Conclusion
The combination of these two services enables the operation team to have the right tool to monitor and react for any kind of incident. Root cause analyzes can be done fast by consolidating these two services.

Comments

Post a Comment

Popular posts from this blog

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

By
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(
Post a Comment
Read more

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

By
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
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 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
Post a Comment
Read more