Missing metrics

Watch 01
HTTP/2SQLgRPCUsers1,200 req/sAPI server1 vCPU · 1 GB × 2Postgres1 vCPU · 2 GBChange capt…
HTTP/2SQLgRPCUsers1,200 req/sAPI serverPostgres1 vCPU · 2 GBChange ca…

Fix the board. Turn every goal green.

Traffic
1,200 req/s · up to 2,400 req/s · reads only
Limit
API server answers about 6,700 req/s
Bill
  • API server8 USD/mo
  • Postgres8 USD/mo
  • Change capture1 USD/mo
17 of 36 USD/mo

Goals

Not tested yet

99 of 100 requests finish faster than this.The share of requests that fail or get no answer.What the servers and services cost each month.

A sale doubles traffic to 2,400 pages/s at 0:30. Page p99 rises from 26 ms to over 10 s. The only graph on the dashboard is API CPU, and it stays near 36 percent. Find the cause. Keep p99 under 100 ms and errors under 0.1 percent. Budget: 36 USD/mo. At most 4 edits.

00:30 UTC. Page p99 jumps from 26 ms to 10 s. Dashboard: requests and API CPU (36 percent). No disk or queue graph.

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: Redis cache, Memory cache, API server. At most 6 parts. Budget: 36 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.