Continuous Profiling on AKS with Pyroscope, Blob Storage, and Managed Grafana
· 20 min read
Post Updates
2026-05-20 — Updated based on lessons learned from a live deployment:
- Removed hardcoded
pyroscope.image.tagfromvalues-azure.yamlto prevent chart/image version mismatches when the chart is upgraded - Added
pyroscope.extraLabelswithazure.workload.identity/use: "true"to propagate the label to all pod templates (the chart usesextraLabels, notpodLabels) - Pinned
--version 2.0.1in thehelm upgrade --installcommand - Added a Troubleshooting callout documenting the two most common crash patterns and their fixes
You deploy your workloads on AKS and collect metrics with Prometheus and logs with Loki. But when latency spikes hit, you stare at dashboards knowing something is slow without knowing where in your code the time is being spent.
That's the gap continuous profiling fills.
