Temporal
Forward Temporal workflow logs to Sazabi for durable execution observability.
Forward your Temporal workflow logs directly to Sazabi for comprehensive observability of your durable execution platform. Monitor workflows, activities, and worker performance with AI-powered analysis.
About this data source
Temporal provides durable execution for long-running workflows and reliable distributed systems. By forwarding logs to Sazabi, you can:
- Monitor workflow executions and state transitions
- Track activity completions and failures
- Analyze worker performance and task queue health
- Detect stuck workflows and long-running activities
- Use AI to investigate complex workflow issues
Prerequisites
Before you begin, make sure you have:
- Access to your Temporal Cloud namespace or self-hosted cluster
- Appropriate permissions to configure visibility and export
- 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
Access Temporal settings
For Temporal Cloud, navigate to your namespace settings in the Temporal Cloud console. For self-hosted clusters, access your cluster configuration.
Configure log export
Set up workflow history and visibility export to Sazabi's intake endpoint:
- Endpoint:
https://temporal.<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.
Configure worker logging
Update your worker configuration to forward logs using OpenTelemetry. Set the standard OTEL environment variables:
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.<region>.intake.sazabi.com
OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer <your-api-key>"Verify configuration
Save your settings and restart workers if needed. Logs will begin flowing to Sazabi when workflows execute.
Log types
Temporal log forwarding includes:
- Workflow events: Start, complete, fail, timeout, and continue-as-new
- Activity events: Scheduled, started, completed, failed, and timed out
- Worker metrics: Poll success/failure, task processing times
- Timer events: Timer created, fired, and canceled
- Signal events: Signals sent and received
Verifying logs are flowing
Once configured, verify that logs are flowing to Sazabi:
-
Trigger a workflow: Start a workflow execution in your Temporal namespace.
-
Ask the assistant: Open a thread in Sazabi and ask "Show me recent Temporal workflow executions" or "What workflows failed in the last hour?"
Troubleshooting
Logs not appearing in Sazabi
- Verify export is configured in your Temporal namespace
- Check that worker OTEL configuration is correct
- Ensure the endpoint URLs include the correct region
- Start a workflow to generate events
401 Unauthorized errors
- Your API key may be invalid or expired
- Verify the Authorization header format
- Create a new public API key in Settings > API Keys
Missing workflow history
For complete workflow history export, ensure your Temporal plan supports visibility export or that your self-hosted cluster is configured correctly.
Worker logs missing
Verify your workers have the OpenTelemetry SDK configured and the environment variables are set correctly.