OTLP traces
Send OpenTelemetry traces to ingest.sensobit.com over HTTP.
Sensobit accepts OTLP/HTTP traces and stores them in Tempo. Use the standard OTLP path so existing SDKs work without a custom exporter.
Endpoints
| Path | Notes |
|---|---|
https://ingest.sensobit.com/v1/traces | Standard OTLP HTTP |
https://ingest.sensobit.com/api/v1/traces | Alias used by some agents |
Content types: application/x-protobuf (default for most SDKs) and application/json.
OpenTelemetry Collector
exporters:
otlphttp:
endpoint: https://ingest.sensobit.com
traces_endpoint: https://ingest.sensobit.com/v1/traces
headers:
X-API-Key: YOUR_API_KEY
X-Sensobit-Namespace: production
service:
pipelines:
traces:
receivers: [otlp]
exporters: [otlphttp]Language SDK (Node.js)
const { NodeSDK } = require('@opentelemetry/sdk-node');
const { OTLPTraceExporter } = require('@opentelemetry/exporter-trace-otlp-http');
const sdk = new NodeSDK({
traceExporter: new OTLPTraceExporter({
url: 'https://ingest.sensobit.com/v1/traces',
headers: {
'X-API-Key': process.env.SENSOBIT_API_KEY,
'X-Sensobit-Namespace': 'production',
},
}),
});
sdk.start();Agent as a local OTLP receiver
The host agent can listen on port 4318 and forward spans:
traces:
enabled: true
otlp_port: 4318
enable_otlp: true
batch_size: 100
interval: 10sPoint in-cluster or on-host SDKs at http://localhost:4318. Keep this disabled unless you need a node-local collector.
Inspect traces
Open Traces or APM in the console. Public query routes live on api.sensobit.com and are listed in the REST overview.