Ref: https://docs.microsoft.com/en-us/azure/azure-monitor/snapsho...
It works even better with DevOps source indexing added to the build pipeline:
https://docs.microsoft.com/en-us/azure/devops/pipelines/task...
A vaguely similar feature is Azure App Service memory leak diagnostic tools which take memory dumps on certain triggers or at intervals.
You can open these in Visual Studio and it’ll show the heap deltas over time.
Most of these couldn't be reproduced either. As in, you'd get a crash once a day in a page that would otherwise work successfully thousands of times.
How would you fix a problem where there's a stack trace only from a release? The scenario is: you can't reproduce the errors, you don't get line numbers, you don't even get function argument values.
I could solve these in minutes using this tool. Could you match that without such tooling?
My demo is to pick a random crash and diagnose the root cause while talking. The mean time to resolution is low single digit minutes.
I showed this to an entire team, one person at a time, solving bugs as I went. I showed the junior devs, senior devs, and their manager.
No interest. None. Just… silence.
The tools are amazing, but the lack of motivation from the typical developers for learning to use them is even more amazing.