Picture a nightly batch that calls a partner API thousands of times. Three nights out of seven a handful of calls time out, the job retries, everything eventually succeeds, and nobody finds a single error in the code. If those machines reach the internet through a public load balancer, the culprit has a name: Azure SNAT exhaustion. Here is how to recognise it, measure it in Dynatrace SaaS, and decide when it deserves a page.
A word of candour first: span.observer did not replay these queries on a live subscription. The Azure facts come from Microsoft’s pages on outbound connections and Load Balancer diagnostics . The DQL is assembled from the Dynatrace documentation and flagged as not executed.
The scope is deliberately narrow: the collection described belongs to Azure Cloud Platform Monitoring, presented as a Dynatrace SaaS service. Nothing was checked for Dynatrace Managed, so do not carry these settings over without its own documentation.…