Inngest
Instrument the application that hosts your Inngest functions with the OpenTelemetry SDK and point it at a Sazabi endpoint to forward logs and traces.
About
Forward logs and traces from your Inngest-served application into Sazabi. Inngest does not emit OpenTelemetry on its own — you instrument the host application and point it at a Sazabi endpoint. That streams in logs and traces for your function executions.
Prerequisites
- A self-hosted Inngest serve endpoint (a Next.js, Express, Bun/Node, or similar handler) to instrument. Functions defined only in Inngest Cloud have no host runtime to add the OpenTelemetry SDK to.
- An OpenTelemetry SDK compatible with your application runtime.
- Your Sazabi intake URL, shown above — open the log source and copy the Intake URL from its setup screen (the public key is embedded in the URL).
Set up in the dashboard
Instrument the host application
Add the OpenTelemetry SDK to the application that serves your Inngest functions and initialize it before the application handles requests. Most languages have official OpenTelemetry SDKs available (for example @opentelemetry/api for Node.js, opentelemetry-api for Python).
Set the following environment variables so they are present when the process starts:
OTEL_EXPORTER_OTLP_ENDPOINT— your intake URL (shown above)OTEL_EXPORTER_OTLP_PROTOCOL—http/protobuf
Redeploy the application
Redeploy or restart the application that serves your Inngest functions so it picks up the new environment variables and SDK initialization.
Set up with the CLI
You can also register the Inngest 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 inngest --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
Invoke an Inngest function to generate fresh telemetry. Open the Intake page in the Sazabi dashboard and confirm logs and traces from the Inngest source appear. Records typically arrive within a minute or two of the function invocation.
Troubleshooting
No telemetry after invoking a function — Confirm OTEL_EXPORTER_OTLP_ENDPOINT is set in the process that hosts the Inngest serve handler, not only in a build step. Check the application logs for OpenTelemetry SDK initialization errors.
Traces appear but logs do not — Confirm your OpenTelemetry SDK initialization exports log records, not only traces. Some SDK setups enable tracing by default and require log export to be configured explicitly.
Metrics are not stored — Sazabi does not store OpenTelemetry metrics sent to this endpoint.