Azure Traffic Manager
DNS-based global traffic load balancer that steers clients to healthy endpoints across regions.
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| anycast | boolean | — | no | false | inherited |
| geoRouting | boolean | — | no | false | inherited |
| healthChecked | boolean | — | no | false | ▸ true |
| managed | boolean | — | no | true | ▸ true |
| monitorProtocol | enum | http | https | tcp | no | — | inherited |
| probeTimeoutSeconds | integer | — | no | 10 | inherited |
| probingIntervalSeconds | integer | — | no | 30 | inherited |
| redundantProviders | boolean | — | no | false | inherited |
| routingMethod | enum | priority | weighted | performance | geographic | multivalue | subnet | no | — | inherited |
| toleratedFailures | integer | — | no | 3 | inherited |
| ttlSeconds | integer | — | no | — | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
shared-dependency-without-redundancy
The design requires redundant discovery, but this DNS or coordination service, which everything depends on, runs on a single provider or a single replica. Its failure is the whole system's failure.
- — all of these hold:
- — the design requirement `availability.discoveryRedundant` is true
- — any of these hold:
- — the node's `redundantProviders` is false
- — the node's `replicated` is false
nodes:
- { id: "traffic-manager", component: "azure-traffic-manager" }Alibaba Cloud DNSalibaba-dnsAlibaba Cloud Domain Namesalibaba-domainsAlibaba Cloud DNS PrivateZonealibaba-private-zoneAmazon Application Recovery Controller (ARC)aws-application-recovery-controllerAmazon Route 53 Global Resolveraws-route53-global-resolverAmazon Route 53 Resolver endpointaws-route53-resolverAmazon Route 53route53Azure DNSazure-dnsAzure DNS Private Resolverazure-dns-private-resolverAzure Private DNSazure-private-dnsCloudflare DNScloudflare-dnsCloudflare Internal DNScloudflare-internal-dnsCloudflare Registrarcloudflare-registrarCloudflare Secondary DNScloudflare-secondary-dnsBIND 9bindCoreDNScorednsGeneric DNSdnsDNSdns-resolverdnsmasqdnsmasqExternalDNSexternal-dnsKnot DNSknot-dnsIBM NS1 Connectns1Pi-holepi-holePowerDNS Authoritative ServerpowerdnsUnboundunboundDigitalOcean DNSdigitalocean-dnsGoogle Cloud DNSgoogle-cloud-dnsCloud Domainsgoogle-cloud-domainsIBM Cloud DNS Servicesibm-dns-servicesDNS Private Zoneoci-dns-private-zoneDNS Public Zoneoci-dns-zoneTraffic Management Steering Policyoci-traffic-managementOpenStack Designateopenstack-designate
# yaml-language-server: $schema=../../schema/component.schema.json # Azure Traffic Manager: DNS-based global traffic load balancer with per-profile endpoint # monitoring. "Azure Traffic Manager endpoint monitoring": monitoring is enabled by default, # probing interval defaults to 30 seconds, tolerated failures to 3 and probe timeout to 10 seconds. schemaVersion: "1" type: "component" id: "azure-traffic-manager" kind: "dns" provider: "azure" docs: "https://learn.microsoft.com/en-us/azure/traffic-manager/traffic-manager-overview" defaults: managed: true healthChecked: true properties: routingMethod: type: "enum" values: ["priority", "weighted", "performance", "geographic", "multivalue", "subnet"] monitorProtocol: type: "enum" values: ["http", "https", "tcp"] probingIntervalSeconds: type: "integer" default: 30 toleratedFailures: type: "integer" default: 3 probeTimeoutSeconds: type: "integer" default: 10