Data Flow

Sazabi works with your observability data in two complementary ways: data sources that send logs into Sazabi, and backends where Chat queries logs. Understanding this distinction helps you configure Sazabi for your infrastructure.

How data flows through Sazabi

DATA SOURCES                        BACKENDS
(Sending Data)                      (Querying Data)

+-------------------+               +-------------------+
|  Your Platform    |               |  Your Platform    |
|  (Vercel, AWS)    |               |  (Datadog, AWS)   |
+-------------------+               +-------------------+
         |                                   ^
         | logs                              | query
         v                                   |
+-------------------+               +-------------------+
|     Sazabi        |               |     Sazabi        |
|     Storage       |               |     Chat          |
+-------------------+               +-------------------+

Data flows FROM                     Sazabi queries
your platform TO Sazabi             your platform directly

Data sources vs backends

Data sources

Data sources send a copy of your logs to Sazabi. The data is stored in Sazabi's managed ClickHouse backend, giving you:

• Fast full-text search across all your logs
• AI-optimized indexing and analysis
• Configurable retention (default 30 days)
• Unified storage across all your platforms

Sazabi supports two types of data sources:

• Native data sources: Sazabi provisions and manages the forwarding infrastructure automatically. Connect your account, and logs start flowing.
• Manual data sources: You configure your platform to send logs to Sazabi's intake endpoint. This gives you full control over what data is sent.

Backends

Backends let Sazabi query your existing observability platform directly. Instead of storing a copy of your data, Sazabi authenticates with your platform and fetches logs on demand when Chat needs them.

This is useful when:

• You have compliance requirements that prevent data duplication
• You want to keep using your existing observability tooling
• You have significant historical data you do not want to migrate

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

Intake monitoring

The Intake page provides real-time visibility into your log ingestion pipeline. Use it to monitor data volume, verify data sources are active, and diagnose ingestion issues.

Next steps