Monitor Baseten Model Logs with SigNoz via OpenTelemetry

Overview

Baseten is a platform for deploying and serving machine learning models. Baseten ships its logs to SigNoz over OTLP/HTTP using a built-in OpenTelemetry connection.

Prerequisites

A Baseten organization, with permission to edit organization settings
An instance of SigNoz (either Cloud or Self-Hosted)

Configure the OTEL Connection

Add the connection in Baseten

In the Baseten console, go to Settings > General and find the OTEL connection card.
Click Add connection.
Configure the fields:

Endpoint URL: https://ingest.<region>.signoz.cloud:443/v1/logs
Header name: signoz-ingestion-key
Header value: <your-ingestion-key>

Save the connection.

Add OTEL configuration dialog in Baseten with SigNoz endpoint and signoz-ingestion-key header — *OTEL connection configured for SigNoz in Baseten*

Verify these values:

<region>: your SigNoz Cloud region
<your-ingestion-key>: your SigNoz ingestion key

Test the connection

Click Test in the connection dialog (Baseten also fires this probe when you save). It posts a Baseten OTLP connection test log to your endpoint. Open Logs in SigNoz and search for the baseten.telemetry_export_test scope to confirm the endpoint and ingestion key work.

Exports start once the connection is enabled. Baseten does not backfill older logs.

Validate

Trigger activity in Baseten. For example, send a prediction to a deployed model, or redeploy one.
Open Logs in SigNoz. Within a few minutes, your Baseten logs appear as log entries.
Filter on service.name = baseten to see all Baseten logs. You can also narrow it down by model_id or model_version_id to scope to one model.

Baseten model logs in the SigNoz Logs explorer filtered by service.name baseten — *Baseten logs in the SigNoz Logs explorer*

Troubleshooting

No data appearing

Confirm the Endpoint URL ends in /v1/logs and matches your SigNoz Cloud region.
Confirm the Header name is exactly signoz-ingestion-key and the Header value is a valid ingestion key. Copy it fresh from SigNoz settings.
Confirm the connection is enabled and that Baseten is generating logs. Exports start when you enable the connection and do not include older logs.
Search service.name = baseten. If the baseten.telemetry_export_test probe appears but model logs do not, the pipe works and you only need to generate activity (deploy a model, or send a prediction).

Replacing an existing destination

A Baseten organization supports one OTLP destination at a time. If logs already go elsewhere, update or remove that connection before you point Baseten at SigNoz.

Limitations

Logs only: Baseten exports logs. Traces and metrics are not supported.
One destination: each organization supports one OTLP destination at a time.
No backfill: exports cover logs generated after you enable the connection.

Next Steps

Set up log-based alerts to detect error patterns from a specific model or version.
Build dashboards to visualize Baseten model logs in a single view.
Monitor Baseten from your application code with OpenTelemetry to get traces, logs, and metrics from the calling side.

Get Help

If you need help with the steps in this topic, please reach out to us on SigNoz Community Slack. If you are a SigNoz Cloud user, please use in product chat support located at the bottom right corner of your SigNoz instance or contact us at cloud-support@signoz.io.