> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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](https://docs.sazabi.com/guides/instrument/metrics.md).

## 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](https://docs.sazabi.com/guides/instrument/traces.md).

## 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](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/webhook-events.md).

## Why this matters for investigation

Because each signal becomes a searchable record, the agent can query logs, metrics, traces, and events in one investigation. The answer includes the records and queries it used, while trace identifiers, metric labels, and structured log fields preserve signal-specific context.

## Further reading

> [card] [Browse the log source catalog](https://docs.sazabi.com/catalogs/log-sources.md)
>
> Find your platform and its setup steps.

> [card] [Send metrics](https://docs.sazabi.com/guides/instrument/metrics.md)
>
> Send and query metrics.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.