This guide will help you set up the OpenTelemetry Collector on your own server and connect it with Hoppscotch. Hoppscotch will send telemetry data (traces and metrics) to your OpenTelemetry Collector instance. From the Hoppscotch Admin Dashboard, you can easily configure the connection to your deployed Collector.Documentation Index
Fetch the complete documentation index at: https://docs.hoppscotch.io/llms.txt
Use this file to discover all available pages before exploring further.

Architecture Overview
- Hoppscotch sends telemetry data to your OpenTelemetry Collector.
- The Collector processes this data and exports it to your preferred backends:
- Jaeger (traces)
- Prometheus (metrics)
- Grafana (visualizations, via Prometheus)
- You can also enable debugging by exporting logs directly to the console.
Step 1: Configure OpenTelemetry Collector
Step 1: Configure OpenTelemetry Collector
Create a configuration file named
otel-collector-config.yaml:Step 2: Configure Prometheus
Step 2: Configure Prometheus
Create a file named
prometheus.yml:Step 3: Configure Grafana Data Source
Step 3: Configure Grafana Data Source
Provision Grafana with Prometheus as a data source.Create
grafana/provisioning/datasources.yaml:Step 4: Docker Compose Setup
Step 4: Docker Compose Setup
Use the following
docker-compose.yaml to deploy everything:Step 5: Run the Stack
Step 5: Run the Stack
Start the observability stack:
- Jaeger UI: http://localhost:16686
- Prometheus: http://localhost:9090
- Grafana: http://localhost:3000
Step 6: Connect Hoppscotch
Step 6: Connect Hoppscotch
From the Hoppscotch Admin Dashboard, configure the OpenTelemetry Collector endpoint (HTTP).