Production problems rarely arrive with useful details. Customers report that checkout is slow, an order failed, or something simply did not work. Developers must determine whether the problem lives in the browser, API, database, a dependency, or the latest code change.

In this demo-driven session, you’ll see how Azure Application Insights helps developers follow real customer journeys across a modern React, ASP.NET Core, and Azure SQL application. We’ll use Playwright to generate realistic traffic, then investigate slow requests, API failures, browser exceptions, dependency bottlenecks, and suspicious runtime behavior.

You’ll see how distributed tracing, transaction analysis, custom telemetry, KQL, alerts, and release correlation turn vague symptoms into actionable evidence. Finally, we’ll bring those findings back to the repository and use GitHub Copilot to understand the affected code, identify likely causes, and propose a safe fix.

This is observability for application developers, focused on finding the problem, fixing the right code, and verifying the customer experience.

Takeaways
Trace production problems across the browser, API, and database.
Use telemetry to isolate failures and performance hotspots.
Turn production evidence into safer fixes with GitHub Copilot.