Intake Monitoring
Monitor ingestion volume, data source activity, and ingestion health for your project.
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.
Accessing the Intake page
Navigate to Intake in the left sidebar, or press i from anywhere in the
dashboard.
The Intake page is only available for projects using the Sazabi-managed logging backend. Projects configured with external backends (Datadog, CloudWatch, etc.) do not display intake metrics.
Summary metrics
The top of the page displays two key metrics for the selected time range:
| Metric | Description |
|---|---|
| Total | Total bytes ingested across all data sources |
| Rate | Current ingestion rate in bytes per hour |
The rate metric includes a status indicator showing whether ingestion is operating normally. A healthy pipeline shows consistent throughput matching your expected log volume.
Ingestion volume chart
The stacked bar chart visualizes bytes ingested over time, broken down by data source. Each data source appears as a distinct color in the stack.
Time ranges
Select a time range using the presets in the top right:
| Range | Bucket size |
|---|---|
| 1h | 5-minute buckets |
| 6h | 15-minute buckets |
| 24h | 1-hour buckets |
| 7d | 1-hour buckets with brush zoom |
For the 7-day view, a brush control below the chart allows you to zoom into specific time periods. Drag the handles to adjust the visible range.
Interacting with the chart
- Hover over any bar to see a tooltip with the exact byte count per data source for that time bucket.
- Filter sources using the data source dropdown to show or hide specific sources in the chart.
- Identify spikes by looking for unusually tall bars, which may indicate logging bursts or configuration changes.
Data source activity table
Below the chart, a table lists all data sources with recent ingestion activity:
| Column | Description |
|---|---|
| Source | Data source name and type |
| Last ingestion | Timestamp of the most recent log received |
| Rate | Current ingestion rate for this source |
Per-key breakdown
Expand any row to see ingestion metrics broken down by API key. This helps you:
- Identify which API keys are actively sending data
- Spot keys that have stopped ingesting
- Correlate traffic patterns with specific deployment environments
Click Manage keys to navigate directly to API key settings where you can create, rotate, or revoke keys.
Diagnosing ingestion issues
Use the Intake page to troubleshoot common problems:
No data appearing
- Check that your data source is configured correctly in Settings > Data Sources.
- Verify your API key is valid and not revoked in Settings > API Keys.
- Confirm your application is running and generating logs.
- Check for network issues between your infrastructure and Sazabi intake endpoints.
Data source stopped ingesting
Look for a data source with a stale "Last ingestion" timestamp. Common causes:
- Deployment rolled back or crashed
- API key rotated but not updated in your application
- Network connectivity issues
- Cloud provider log forwarding disabled
Unexpected volume spikes
Spikes in the chart may indicate:
- Increased error rates causing more logging
- Debug logging accidentally enabled in production
- New services deployed without log volume estimation
- Log forwarding configuration changes
Use the data source filter to isolate which source is responsible, then investigate using Chat.
Onboarding state
If no data sources are configured, the Intake page displays an empty state with quick actions to get started:
- Connect a data source: Set up native or manual log forwarding
- Create an API key: Generate keys for manual data sources
Once at least one data source is sending logs, the page switches to the standard monitoring view.