Inngest
Forward Inngest function logs to Sazabi for workflow and background job observability.
Forward your Inngest function logs directly to Sazabi for comprehensive observability of your background jobs and event-driven workflows. Monitor function executions, retries, and event flows.
About this data source
Inngest provides durable functions for background jobs, scheduled tasks, and event-driven workflows. By forwarding logs to Sazabi, you can:
- Monitor function runs, step executions, and event processing
- Detect failure patterns and retry storms
- Analyze function performance and latency
- Correlate Inngest events with logs from your other services
- Use AI to investigate workflow issues
Prerequisites
Before you begin, make sure you have:
- An Inngest account with deployed functions
- Access to the apps and environments you want to monitor
- A Sazabi public API key (project-scoped)
Get your API key
Create a public key
Click Create API key and select Public as the key type. Public keys are scoped to a single project.
Copy the key and store it securely. You will not be able to see it again.
Setup
Open Inngest Dashboard
Navigate to your Inngest dashboard and select the environment you want to monitor.
Configure log forwarding
Go to Settings > Integrations or Settings > Observability and configure log forwarding to Sazabi's intake endpoint.
- Endpoint:
https://inngest.<region>.intake.sazabi.com - Authorization:
Bearer <your-api-key>
Replace <region> with your Sazabi project region (e.g., us-east-1) and
<your-api-key> with your Sazabi public API key.
Select what to forward
Choose which data to forward:
- Function logs: Output from your function executions
- Event data: Incoming events and their payloads
- Step results: Results from individual workflow steps
- Error details: Stack traces and error metadata
Save and verify
Save your configuration. Logs will begin flowing to Sazabi when functions execute.
Log types
Inngest log forwarding includes:
- Function runs: Start, completion, and failure events
- Step executions: Individual step results within workflows
- Event triggers: Incoming events that trigger function runs
- Retry attempts: Failed executions and retry information
- Concurrency events: Queue and throttle behavior
Verifying logs are flowing
Once configured, verify that logs are flowing to Sazabi:
-
Trigger a function: Send an event or wait for a scheduled function to run.
-
Ask the assistant: Open a thread in Sazabi and ask "Show me recent Inngest function runs" or "What Inngest functions failed today?"
Troubleshooting
Logs not appearing in Sazabi
- Verify log forwarding is enabled in Inngest settings
- Check that the endpoint URL includes the correct region
- Ensure the Authorization header is configured correctly
- Trigger a function to generate logs
401 Unauthorized errors
- Your API key may be invalid or expired
- Create a new public API key in Settings > API Keys
Missing function data
Verify you have selected the appropriate data types to forward in your Inngest integration settings.