Integrations
Unblind is built on top of OpenTelemetry (OTEL). This means you can integrate with us using any tool, language, or agent that supports the OTLP protocol.
Whether you are using a standard OTEL Collector, Vector, Grafana Alloy, or direct language instrumentation, the core integration remains the same: point your OTLP exporter to our endpoint and authenticate with your API key.
Before you can make requests to the Unblind API, you will need to grab your API key. You can create one in Settings.
Core Configuration
Regardless of the tool you choose, you will need these three pieces of information to configure your OTLP exporter.
| Setting | Value |
|---|---|
| Endpoint | https://otlp.unblind.dev |
| Protocol | HTTP/Protobuf |
| Header | Authorization: Bearer <API_KEY> |
Integration Options
Choose the integration method that best fits your stack:
Languages & SDKs
Use native OpenTelemetry SDKs for your programming language (Node, Python, Go, Java, Rust, etc.). Perfect for direct instrumentation in your application code.
OpenTelemetry Collector
The recommended way to send data to Unblind. Allows you to buffer, process, and export data to us alongside your existing tools (like Datadog or Prometheus).
Vector
High-performance observability pipeline. Use the opentelemetry sink to offload data to Unblind.
Grafana Alloy
Use the otelcol.exporter.otlphttp component to forward telemetry to Unblind.
Next Steps
- Choose your integration method from the options above
- Configure your OTLP exporter with the endpoint and headers from the Core Configuration section
- Associate telemetry with tenants by adding a
tenant.idattribute to your resource or attributes - Filter metrics (optional) to reduce noise and manage costs
For detailed setup instructions, click on any of the integration options above.