
How to be successful with monitoring in Azure
Monitoring is often the last thing teams think about — and one of the most expensive things to get wrong. In this episode, Chris is joined by Vanessa Bruwer, Senior Engineer on Microsoft’s FastTrack for Azure team, who has spent over 20 years helping organisations build structured observability strategies. Vanessa explains how the FastTrack team runs focused monitoring assessments that take customers from zero to a fully configured Azure Monitor setup — teaching them to fish rather than fishing for them.
The Azure Monitor suite has grown well beyond Log Analytics to encompass Application Insights for application performance monitoring, rich alerting, and distributed tracing — essential for understanding behaviour across microservice architectures. Vanessa and Chris explore why collecting all your telemetry without a strategy is as dangerous as collecting nothing, how alert fatigue sets in, and what a thoughtful observability approach looks like for different workload types.
Key topics covered:
- Why monitoring strategy should be established at build time, not at incident time
- Moving from reactive (waiting for users to report problems) to proactive observability
- The pitfalls of “collect everything” and the alert fatigue spiral
- How to tailor Azure Monitor configuration to workload characteristics — a VM vs a distributed microservice require very different approaches
- The FastTrack for Azure monitoring methodology: structured sessions that leave customers self-sufficient
Whether you are getting started with Azure Monitor or looking to mature your team’s observability practice, this episode provides a practical framework for making monitoring a first-class engineering concern.
Related Content

CGN2 - Cloud Gaming Notes Episode 2 - Matchmaking Services
Ever thought about what it takes to host a multiplayer game in the cloud? In the second episode of Cloud Gaming Notes, Chris and Lee Williams go hands-on with Halo 5 Guardians to explore the engineering behind matchmaking services. They cover the Actor model and Azure Service Fabric, skill-based matchmaking algorithms, the critical role of latency in competitive gaming, and how live ops and DevOps principles keep a game-as-a-service continuously updated without downtime. Real-world cloud architecture through the lens of AAA gaming.

24 - Health Endpoint Monitoring Pattern (Monitor your service and its dependencies!)
Stop waiting for users to tell you something is broken. The Health Endpoint Monitoring pattern gives your services a dedicated health-check endpoint that aggregates the status of all dependent components—databases, APIs, storage—into a single observable response. This episode covers the pattern in detail, including design considerations around caching, security, denial-of-service exposure, and integration with Azure Monitor and Application Insights.

42 - How to choose the 'Right' Datastore for your scenario
With so many data store options in Azure — relational SQL, NoSQL, document databases, blob storage, key-value stores, and more — how do you choose the right one for your workload? In this episode, Chris Reddington is joined by Steph Martin to explore the concept of polyglot persistence and the trade-offs between data store types. From Azure SQL and Cosmos DB to blob storage and microservices data patterns, they discuss how workload requirements, access patterns, RTO/RPO targets, and application architecture should guide your data platform decisions. A practical guide for architects and developers navigating the modern data landscape on Azure.