Before the users

Watch 12
RegionZoneRegionHTTP/2HTTP/2HTTP/2Users600 req/sDNS1 vCPU · 1 GBLoad balanc…1 vCPU · 1 GBAPI server4 vCPU · 4 GBLoad balanc…1 vCPU · 1 GBAPI server4 vCPU · 4 GB
RegionZoneRegionDNSHTTP/2HTTP/2HTTP/2Users600 req/sDNSLoad bala…API serverLoad bala…API server

Turn every goal green.

Traffic
600 req/s · 90% reads
Limit
DNS answers about 10,000 req/s
Bill
  • DNS4 USD/mo
  • Load balancer (L7) × 28 USD/mo
  • API server × 232 USD/mo
44 of 100 USD/mo

Goals

Not tested yet

Time from a fault until an alert fires.The share of requests that get a correct answer.What the servers and services cost each month.

Shoppers in two regions reach the store through DNS, 600 requests/s. At 0:50 the app servers in one eu zone fail, but the eu balancer still looks healthy. Find the outage within 60 s and keep availability above 90 percent. Probe runs cost 0.02 USD per 1,000.

A graph for each resourceTap to add or remove the probes

One CPU graph · CPU 40% · disk no graph · the fault is hidden

Parts you can add: Synthetic checks. At most 10 parts. Budget: 100 USD/mo.

Tap a part to add it, or drag it onto a trace.Click a part to add it, or drag it onto a trace.