Instrument

Everything you investigate in Sazabi starts as data you send in. There are two ways to set up a log source: connect a supported platform account so Sazabi pulls your logs, or point a collector, SDK, or agent at your project'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.

You get the intake URL from Settings > Log streams: 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 for advanced use.

Two ways to set up a log source

Pick by where your data lives.

• Connect your account — authorize Sazabi to pull logs from a supported platform. Use this when your platform is in the catalog's Connect-your-account list (for example Vercel, Cloudflare, or Sentry).
• 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.

For a decision guide, see Choosing an ingestion path.

Browse the log source catalog

Every supported source is documented per vendor in the log source catalog, split by the same two paths. Start there to find your platform and its exact setup steps.

In this section