Metrics
Host, container, service, database and custom metrics, aligned in time.
One timeline
Metrics, logs, traces, profiles, replay and database statements are captured once by the agent, time-aligned and linked.
- Signal types
- 6
- Capture layer
- 1
- Timeline
- 1
- Extra instrumentation
- 0
OverviewDiting
Signals link to each other
Click a spike and land on the trace. Jump from a trace to its logs. From a log to the session. Context survives every hop.
Metrics, logs, traces, profiles, databases, sessions
Logs
Collect, search, add context and alert without changing log formats.
Traces
Distributed traces, waterfalls and error attribution, with SQL inside spans.
Sessions
Browser replay, linked both ways with traces and logs.
Profiles
CPU and memory hotspots attributed to functions and kernel stacks.
Database
Statements and plans parsed on the wire, no driver.
How signals line up
| Time | Unified timestamps and clock correction across hosts |
|---|---|
| Keys | trace_id, session_id, host_id, service, pod |
| Retention | Configured per signal, hot and warm tiers |
| Ingest | Agent capture, plus OTLP |
Fits
- Complex systems that need cross-signal context
- Teams already running OTLP pipelines
Doesn't fit
- A single dashboard with no need for correlation
Bring your system in
Tell us what you run: OS, kernel, public network or not, virtual machines or clusters. We will map the path in.