Log sampling

Watch 04
HTTP/2HTTP/2HTTP/2HTTP/2HTTP/2Partner apps200 req/sPartner apps20,000 req/sRate limiter1 vCPU · 1 GBRate limiter1 vCPU · 1 GBManaged que…2 vCPU · 1 GBLog store2 vCPU · 2 GB
HTTP/2HTTP/2HTTP/2HTTP/2HTTP/2Partner a…200 req/sPartner a…20,000 req/sRate limi…1 vCPU · 1 GBRate limi…1 vCPU · 1 GBManaged q…2 vCPU · 1 GBLog store2 vCPU · 2 GB

Tune the parts. Turn every goal green.

Traffic
Errors200 req/s · up to 3,000 req/s · writes onlyInfo20,000 req/s · writes only
Bill
  • Rate limiter × 28 USD/mo
  • Managed queue8 USD/mo
  • Log store8 USD/mo
24 of 4,600 USD/mo

Goals

Not tested yet

The share of requests that fail or get no answer.Requests served each second.What the servers and services cost each month.

A fleet sends 20,000 info lines/s and 200 error lines/s. In an incident, errors reach 3,000/s for 30 s. A managed intake bills each line. A sampler splits its limit between the two classes. Set both limits. Keep 99 percent of errors and 400 info lines/s. Stay under 4,600 USD/mo.

A graph for each resourceTap to add or remove the probes

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