Product · Cross-signal investigation

Keep the incident together as the question changes.

Move metric → trace → profile or log → host and back while the investigation stack preserves each frame, time anchor, and entity filter.

Context is a first-class product object.

The operator should not have to remember every filter they used to reach the current answer.

Push up to six frames as the incident narrows, pin important evidence, and navigate backward or forward.

Use correlation routes and trace/span profile links to prefill filters instead of stitching context only in the browser.

Zoom once and propagate the relevant window into every signal panel opened from the frame.

Use the command palette and investigation bindings to change scope without losing the analytical thread.

workflow

Each step changes the question while preserving the evidence that motivated it.

101 · Symptom
Open the metric anomaly
Capture the service, tenant, labels, and time window that define the change.
202 · Request
Inspect representative traces
Find the failing dependency or span without copying the time range into another backend.
303 · Event
Open correlated logs
Carry the trace ID and time anchor into structured event search.
404 · Re-evaluate
Move backward without starting over
Compare a neighboring trace or widen the time window from the previous investigation frame.

proof / shipped

Logs, metrics, and traces share the same storage, time, and tenant model. Profile metadata uses that context while raw pprof remains portable.

Product · Cross-signal investigation

Move metric → trace → profile or log → host and back while the investigation stack preserves each frame, time anchor, and entity filter.