Skip to main content

Should I use Azure Monitoring or Azure Service Health?

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

Popular posts from this blog

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...