Overview

Send logs from your platforms to Sazabi so Chat can analyze them, detect anomalies, and help you debug production issues faster.

How log ingestion works

When you send logs to Sazabi, your data flows through our intake pipeline:

1. Authenticate: Your platform sends logs using a public API key that identifies your project.
2. Ingest: Logs arrive at regional intake endpoints optimized for low latency.
3. Store: Sazabi stores your logs in our high-performance backend, indexed for fast querying.
4. Analyze: Chat can now search, correlate, and investigate your logs.

Each project has its own public API key, which you can find in Settings > API Keys in the dashboard.

Two ways to send logs

Sazabi supports two approaches for getting logs into the platform:

Native data sources

With native data sources, Sazabi handles the integration work for you. You authenticate with your cloud provider, and Sazabi automatically provisions the necessary infrastructure to forward logs.

Supported native data sources:

• AWS CloudWatch Logs
• Google Cloud Logging
• Vercel
• Convex
• DigitalOcean
• Fly.io
• Render

Manual data sources

With manual data sources, you configure your platform to send logs directly to Sazabi's intake endpoint. This approach works with any platform that supports standard log forwarding protocols.

Supported manual data sources:

• OpenTelemetry (OTLP)
• Datadog Agent
• Sentry SDK
• PostHog
• Supabase
• Cloudflare
• Inngest
• Temporal
• Mastra
• LangChain
• Daytona
• Railway
• E2B
• Netlify

Coming soon

We are actively working on integrations for additional platforms. See Coming Soon for details and waitlist signup.

Data sources vs backends

Sazabi can work with your observability data in two different ways. It is important to understand the difference:

DATA SOURCE (Sending Logs)
+-------------------+         +-------------------+
|  Your Platform    | ------> |     Sazabi        |
|  (e.g. AWS CW)    |  logs   |    Storage        |
+-------------------+         +-------------------+
Data flows FROM your platform TO Sazabi

BACKEND (Querying in Place)
+-------------------+         +-------------------+
|  Your Platform    | <------ |     Sazabi        |
|  (e.g. AWS CW)    |  query  |    Chat           |
+-------------------+         +-------------------+
Sazabi queries your platform WITHOUT moving data

Data sources send a copy of your logs to Sazabi. The data is stored in Sazabi's backend, giving you fast queries, long retention, and full AI analysis capabilities.

Backends let Sazabi query your existing observability platform directly. Your data stays where it is, and Sazabi fetches what it needs on demand. This is useful when you have compliance requirements or want to avoid data duplication.

Some platforms support both modes. For example, AWS CloudWatch can be configured as a data source (forwarding logs to Sazabi) or as a backend (Sazabi queries CloudWatch directly).

What happens to your logs

When logs arrive at Sazabi:

• Storage: Logs are stored in our ClickHouse-based backend, optimized for fast analytical queries.
• Retention: Default retention is 30 days. Enterprise plans support custom retention periods.
• Indexing: Logs are automatically indexed for full-text search and structured queries.
• AI access: The Sazabi assistant can search, filter, and analyze your logs to help you investigate issues.

Your logs are encrypted at rest and in transit. Sazabi does not share your data with third parties or use it to train AI models.

Next steps