Metric cardinality

Watch 03
HTTP/2HTTP/2HTTP/2HTTP/2Partner apps200 req/sPartner apps96 req/sPartner apps60 req/sPartner apps40,000 req/sTime series…6 vCPU · 8 GB
HTTP/2HTTP/2HTTP/2HTTP/2Partner…Partner…96 req/sPartner…60 req/sPartner…Time se…

Fix the board. Turn every goal green.

Traffic
Route series200 req/s · writes onlyLatency series96 req/s · writes only2 more
Limit
Time series DB answers about 60,000 writes/s
Bill
  • Time series DB32 USD/mo
32 USD/mo in total

Goals

Not tested yet

The share of requests that fail or get no answer.The share of requests that fail or get no answer.The share of requests that fail or get no answer.

A 400 GB metrics store gets points from four exporters. Disk use grows 84 GB/day and the store fills on day 5, so dashboards and alerts go blind. Keep route, latency and tenant metrics for 14 days with no gaps. Keep disk under 320 GB. The store is locked. At most 3 edits.

Day 5, 19:00 UTC. Metrics store disk is full. Dashboards and alerts are empty. Graph: disk use up 84 GB/day for 5 days.

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: Log store. At most 3 parts.

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