OpenTelemetry Collector
Add an otlphttp exporter to your OpenTelemetry Collector configuration to forward logs and traces from your infrastructure to Sazabi.
About
Add a Sazabi exporter to your OpenTelemetry Collector pipeline to forward logs and traces from any existing receiver — Kubernetes container logs, Jaeger, or anything else in the Collector ecosystem. Sazabi acts as an additional OTLP/HTTP destination alongside your existing exporters.
Metrics are not stored by this source. Use OpenTelemetry Metrics for metric data.
Prerequisites
- A running OpenTelemetry Collector deployment (Kubernetes DaemonSet, sidecar, or standalone binary)
- 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
Add the Sazabi exporter to your Collector config
Add an otlphttp/sazabi exporter to your otelcol.yaml and wire it into your logs and traces pipelines:
receivers:
filelog:
include: [/var/log/pods/*/*/*.log]
start_at: beginning
otlp:
protocols:
grpc:
endpoint: 0.0.0.0:4317
http:
endpoint: 0.0.0.0:4318
exporters:
otlphttp/sazabi:
endpoint: <your intake URL>
service:
pipelines:
logs:
receivers: [filelog]
exporters: [otlphttp/sazabi]
traces:
receivers: [otlp]
exporters: [otlphttp/sazabi]Replace <your intake URL> with the intake URL shown above. The URL already encodes your project public key; no additional headers are required.
For Kubernetes deployments using Helm, add the exporter under config.exporters in your values file and add otlphttp/sazabi to your pipeline exporter lists.
Adjust receivers to match your sources
Replace the example receivers with the ones your infrastructure actually uses. Common configurations:
- Kubernetes pod logs — keep the
filelogreceiver pointed at/var/log/pods - Application traces — keep the
otlpreceiver or add ajaegerreceiver - Host metrics — add the
hostmetricsreceiver (metrics will not be stored; use the OpenTelemetry Metrics source for that pipeline)
You can add otlphttp/sazabi to any existing pipeline exporter list alongside your current exporters — the Collector fans out to all configured destinations.
Set up with the CLI
You can also register the OpenTelemetry Collector 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 otel_collector --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
Restart or redeploy the Collector after updating the configuration. Open the Intake page in the Sazabi dashboard and confirm records from the OpenTelemetry Collector source appear within a minute or two.
Troubleshooting
No records after redeploying — Check Collector logs for TLS, DNS, or authentication errors on the otlphttp/sazabi exporter. Confirm the intake URL starts with https:// and is the full URL from above (not the hostname alone).
Logs arrive but traces do not — Verify otlphttp/sazabi is listed in the traces pipeline exporter list, not only the logs pipeline.
Metrics are not stored — This source does not store OpenTelemetry metrics. Use OpenTelemetry Metrics for a metrics pipeline.