Metrics

Every tenant cluster ships an eBPF + ingress telemetry stack, so a deployment has golden signals with zero app instrumentation. One tool reads them.

kubrain deploy metrics myapp
kubrain deploy metrics myapp --window 1h --by component

get_metrics(name, [component], [window], [by]) returns a curated summary:

• request rate — requests/sec
• error rate — 5xx as a fraction (0..1)
• p95 latency — milliseconds
• has_data — false when no traffic was seen in the window

Options

• window — look-back, e.g. 5m (default), 1h, 1d.
• component — narrow to one component’s service; omit for the whole deployment.
• by: component — a row per component; by: pod — a row per replica. Use these to answer which component or which pod.

Read the source

The summary reports its source:

• ingress — measured at the front door (north-south). This p95 is real, end-to-end.
• mesh — east-west/internal, from eBPF (server-side only).

Check it before reasoning about latency — ingress numbers include the network; mesh numbers don’t.

Before you alert

Always read get_metrics before arming an alert — the alert thresholds the same numbers, so a quick read tells you a sane threshold and whether there’s traffic at all.

See also

• Alerting — turn a threshold into a page.