Trigger.dev
Add an OTLP log exporter in trigger.config.ts pointed at your Sazabi intake URL to stream Trigger.dev task logs into Sazabi.
About
Stream Trigger.dev task logs into Sazabi. Set up an OpenTelemetry log exporter in your Trigger.dev project and point it at Sazabi. Trigger.dev has no log-forwarding subscription, so this source sends logs only — straight from the project's own OTLP exporter.
Trigger.dev reserves OTEL_* environment variables for its own internal
telemetry. Do not use them for this log source — configure the exporter
directly in trigger.config.ts as shown below.
Prerequisites
- A Trigger.dev project with a
trigger.config.tsfile. @opentelemetry/exporter-logs-otlp-httpinstalled in the package that ownstrigger.config.ts.- Your Sazabi intake URL (shown above).
Set up in the dashboard
Install the log exporter
Install @opentelemetry/exporter-logs-otlp-http in the package that owns your trigger.config.ts file.
If your project already sets up OpenTelemetry in code, reuse the Sazabi log intake URL in that setup instead of adding a second exporter.
Configure the log exporter
Add the OTLP log exporter to trigger.config.ts:
import { OTLPLogExporter } from "@opentelemetry/exporter-logs-otlp-http";
import { defineConfig } from "@trigger.dev/sdk";
export default defineConfig({
project: "<your-trigger-project-ref>",
telemetry: {
logExporters: [
new OTLPLogExporter({
url: "https://your-intake-host/v1/logs",
}),
],
},
});Replace your-intake-host with the hostname portion of your intake URL (shown above, without https://). The full URL for the log exporter is https://<intake-host>/v1/logs.
Use telemetry.logExporters — not telemetry.exporters. Trace exporters, metrics exporters, alert webhooks, and management API polling are intentionally out of scope for this source.
Redeploy
Redeploy Trigger.dev so it picks up the new log exporter configuration.
Set up with the CLI
You can also register the Trigger.dev log source with the Sazabi CLI (installed and authenticated — see CLI reference).
Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):
sazabi log-sources create trigger_dev --mode connectionlessThe command prints the intake URL for the new source — copy the whole URL and point your sender at it using the configuration shown above. Run sazabi log-sources get <log-source-id> at any time to reprint the endpoint, or sazabi log-sources list to see every log source in the project.
Verify
Run a Trigger.dev task. Open the Intake page in the Sazabi dashboard and confirm task logs from the Trigger.dev source appear. Records typically arrive within a minute or two of the task run.
Troubleshooting
No logs after redeploying — Confirm OTLPLogExporter is in telemetry.logExporters (not telemetry.exporters) in trigger.config.ts and that the url ends in /v1/logs. Check that your Trigger.dev project was redeployed after the config change.
Traces, metrics, or alerts are absent — This source stores logs only. Trigger.dev alert webhooks, management-API polling, traces, and metrics are not supported on this endpoint.