An eelgrass-bay ranger reports one checkout that hung at 14:03. How…

Question

An eelgrass-bay ranger reports one checkout that hung at 14:03. How should the developer locate that single operation in Application Insights?

Accepted Answer

Use transaction search (end-to-end operation search) for that checkout instead of a subscription-wide metric average. — One hung checkout needs transaction/search—find that operation id and walk its timeline. A month-long average chart will never name the 14:03 victim.

Answer

Stare only at a 30-day average failure-rate chart until the one call appears.

Answer

Open an AZ-400 release dashboard and ignore Application Insights entirely.

Answer

Purge the Insights resource so the hung call cannot be found again.

An eelgrass-bay ranger reports one checkout that hung at 14:03. How should the developer locate that single operation in Application Insights?

Short Explanation

Full Explanation