Everything is a log
How Sazabi normalizes logs, metrics, traces, and webhook events into one searchable body of log records through a single intake.
Sazabi treats every kind of telemetry as a log. Whatever you send — application logs, metrics, traces, or webhook events — normalizes into a single searchable body of log records that the Sazabi agent reads during an investigation. You send it all to one intake URL for your project.
One intake for everything
You do not run a separate pipeline per signal type. A single intake accepts your data, normalizes it, and stores it as searchable log records. That means one setup path, one key to manage, and one place the agent looks when you ask a question.
Metrics as logs
Metrics arrive as OpenTelemetry metrics (or Prometheus metrics relayed through an OpenTelemetry Collector) and are stored so that each data point becomes a searchable record. You keep the labels and values; the agent can query them alongside your logs. See Send metrics.
Traces as logs
Traces arrive as OpenTelemetry traces and are stored as records the agent can search and correlate with your logs by trace context. See Send traces.
Webhook events as logs
Platform webhook events — deployment notifications, alerts from other tools, and similar signals — arrive at the same intake and become records you can search. See Webhook events source.
Why this matters for investigation
Because everything is one stream, the agent does not have to stitch together separate systems to answer a question. It searches your logs, metrics, traces, and events together, correlates them, and reasons over the whole picture. That is why the setup work in this group is worth doing once: it makes every later investigation faster.