OpenRouter Observability & Monitoring with OpenTelemetry

SigNoz Cloud - This page applies to SigNoz Cloud editions.
Self-Host - This page applies to self-hosted SigNoz editions.

What is OpenRouter Observability?

OpenRouter observability gives you full visibility into your LLM API routing across multiple models. This guide walks you through setting up OpenRouter monitoring using OpenTelemetry and exporting traces to SigNoz, so you can track requests, latency, and usage across your OpenRouter applications.

With full OpenRouter observability in SigNoz, you can correlate traces across your AI and LLM workflows, configure alerts on latency and errors, and gain actionable insights to continuously improve reliability and responsiveness. SigNoz brings your OpenRouter telemetry into unified dashboards so you can monitor every model request in one place.

Prerequisites

Set Up OpenRouter Observability with OpenTelemetry

Step 1: Configure broadcasting traces from OpenRouter to OTel Collector

For more information on setting up traces from OpenRouter refer to the OpenRouter broadcast guide.

Enable Broadcast in OpenRouter

Go to Settings > Observability and toggle Enable Broadcast.

OpenRouter Enable Broadcast Toggle
OpenRouter Enable Broadcast Toggle

Configure OpenTelemetry Collector

Click 'Add Destination +' next to the OpenTelemetry Collector entry

OTel Collector Add Destination
OpenTelemetry Collector Add Destination

and enter:

  • Endpoint: https://ingest.<region>.signoz.cloud:443/v1/traces
  • Headers:
{
  "signoz-ingestion-key": "<your-ingestion-key>"
}
OTel Collector Add Details
OpenTelemetry Collector Add Details

For self-hosted collector:

  1. Deploy your OpenTelemetry Collector with an OTLP receiver
  2. Configure the receiver to listen on a publicly accessible endpoint
  3. Add the endpoint URL
  4. Remove the ingestion key header as shown in Cloud → Self-Hosted.

Test and Save

Click Test Connection to verify the setup. Once there is a success message, click the "Add" button.

Once configured, your OpenRouter calls are traced and sent to SigNoz.

Step 2: Use the OpenRouter API

For more information on getting started with OpenRouter in your environment, refer to the OpenRouter quickstart guide.

import requests
import json

response = requests.post(
  url="https://openrouter.ai/api/v1/chat/completions",
  headers={
    "Authorization": "Bearer <OPENROUTER_API_KEY>",
    "HTTP-Referer": "<YOUR_SITE_URL>", # Optional. Site URL for rankings on openrouter.ai.
    "X-Title": "<YOUR_SITE_NAME>", # Optional. Site title for rankings on openrouter.ai.
  },
  data=json.dumps({
    "model": "openai/gpt-5.2", # Optional
    "messages": [
      {
        "role": "user",
        "content": "What is SigNoz?"
      }
    ]
  })
)

View OpenRouter Traces in SigNoz

Once configured, your OpenRouter application automatically emits traces.

OpenRouter traces are available in SigNoz under the Traces tab:

OpenRouter Trace View
OpenRouter Trace View

When you click on a trace in SigNoz, you'll see a detailed view of the trace, including all associated spans, along with their events and attributes.

OpenRouter Detailed Trace View
OpenRouter Detailed Trace View

Troubleshooting OpenRouter Observability

If you don't see your telemetry data:

  1. Verify network connectivity - Ensure your application can reach OpenRouter API and SigNoz Cloud endpoints
  2. Check ingestion key - Verify your SigNoz ingestion key is correct
  3. Wait for data - OpenTelemetry batches data before sending, so wait 10-30 seconds after making API calls

OpenRouter Monitoring Dashboard

The OpenRouter Dashboard Template provides ready-made visualizations for monitoring OpenRouter usage. It includes pre-built charts for LLM request volume, token usage, and cost, along with import instructions to get started quickly.

OpenRouter Dashboard
OpenRouter Dashboard Template

Setup OpenTelemetry Collector (Optional)

What is the OpenTelemetry Collector?

Think of the OTel Collector as a middleman between your app and SigNoz. Instead of your application sending data directly to SigNoz, it sends everything to the Collector first, which then forwards it along.

Why use it?

  • Cleaning up data — Filter out noisy traces you don't care about, or remove sensitive info before it leaves your servers.
  • Keeping your app lightweight — Let the Collector handle batching, retries, and compression instead of your application code.
  • Adding context automatically — The Collector can tag your data with useful info like which Kubernetes pod or cloud region it came from.
  • Future flexibility — Want to send data to multiple backends later? The Collector makes that easy without changing your app.

See Switch from direct export to Collector for step-by-step instructions to convert your setup.

For more details, see Why use the OpenTelemetry Collector? and the Collector configuration guide.

Additional resources:

Last updated: June 1, 2026

Edit on GitHub

Was this page helpful?

Your response helps us improve this page.