> ## 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.

# Instrument

> Get your logs, metrics, and traces into Sazabi — connect a supported platform account or send to an endpoint — then verify data is flowing.

Everything you investigate in Sazabi starts as data you send in. There are two ways to set up a log source: use **Native** to connect a supported platform account and let Sazabi configure forwarding, or use **Manual** to configure a collector, SDK, or agent to send to your log source's intake URL. This group covers how ingestion works, how to choose a path, and how to send frontend, metrics, and trace data.

## How ingestion works

You send data to Sazabi's **intake URL** — the keyed endpoint tied to a log stream, with the shape `https://<key>.<region>.intake.sazabi.com`. Copy the whole URL and point your sender at it; because your public key is embedded in the hostname, the URL authenticates the request on its own — there is no separate key or header to send. Sazabi normalizes what arrives — logs, metrics, traces, and webhook events — into a single searchable body of log records that the Sazabi agent queries during an investigation. There is one intake for everything; see [Everything is a log](https://docs.sazabi.com/guides/instrument/everything-is-a-log.md).

You get the intake URL from [**Settings > Log streams**](https://app.sazabi.com/settings/log-source-providers): open your log source and copy the **Intake URL** from its setup screen. The public key embedded in it is a low-level credential most customers never handle directly — it lives under [**Settings > Public keys**](https://app.sazabi.com/settings/api) for advanced use.

## Two ways to set up a log source

Pick by where your data lives.

* **Native — connect your account** — authorize a supported platform account and let Sazabi configure forwarding. Use this when your platform is in the catalog's Connect-your-account list (for example Vercel, Cloudflare, or Sentry).
* **Manual — send to an endpoint** — point a collector, SDK, or agent at your project's intake URL. Use this when you run your own collectors, instrument application code, or your platform is not in the connect-your-account list.

Both modes can stream logs continuously. Manual setup gives you control over the sender and forwarding configuration; it does not mean sending logs by hand.

For a decision guide, see [Choosing an ingestion path](https://docs.sazabi.com/guides/instrument/choosing-a-path.md).

## Browse the log source catalog

Every supported source is documented per vendor in the [log source catalog](https://docs.sazabi.com/catalogs/log-sources.md), split by the same two paths. Start there to find your platform and its exact setup steps.

## In this section

> [card] [Everything is a log](https://docs.sazabi.com/guides/instrument/everything-is-a-log.md)
>
> Why all telemetry normalizes into logs through one intake.

> [card] [Choosing an ingestion path](https://docs.sazabi.com/guides/instrument/choosing-a-path.md)
>
> Decide between connecting an account and sending to an endpoint.

> [card] [The Intake page](https://docs.sazabi.com/guides/instrument/intake.md)
>
> Read ingestion volume and spot anomalies in the dashboard.

> [card] [Log storage & retention](https://docs.sazabi.com/guides/instrument/storage.md)
>
> Where your logs live and how long they are kept.

> [card] [Instrument your frontend](https://docs.sazabi.com/guides/instrument/frontend.md)
>
> Instrument a browser app with the browser SDK or another provider.

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

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

> [card] [Send Kubernetes audit logs](https://docs.sazabi.com/guides/instrument/kubernetes-audit-logs.md)
>
> Send API server audit logs from EKS, GKE, or a self-managed cluster.

> [card] [Manage log streams](https://docs.sazabi.com/guides/instrument/log-streams.md)
>
> Enable, disable, reassign, and delete the streams a source produces.

> [card] [Troubleshooting ingestion](https://docs.sazabi.com/guides/instrument/troubleshooting.md)
>
> Diagnose logs that don't show up or arrive malformed.


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