Send metrics from an OpenTelemetry Collector
Send metrics to Offbeat over OTLP/HTTP using an existing OpenTelemetry Collector. Add Offbeat to the metrics pipeline alongside your current exporters. Keep your traces and logs pipelines pointed at their current destinations.
Create a project ingest key
In Offbeat, open your project and select Ingest keys. Create a key and set OFFBEAT_INGEST_KEY in the Collector's environment to that value.
Configure the OTLP/HTTP exporter
Merge the following settings into your existing Collector configuration. Add otlp_http/offbeat under exporters and append it to the exporter list in your metrics pipeline. Keep the receivers, processors, and exporters already configured for that pipeline.
exporters:
otlp_http/offbeat:
endpoint: https://ingest.offbeat.sh
headers:
authorization: Bearer ${env:OFFBEAT_INGEST_KEY}
service:
pipelines:
metrics:
exporters: [otlp_http/offbeat]The exporter appends /v1/metrics to the endpoint and uses gzip by default. If your Collector version uses otlphttp, useotlphttp/offbeat in both places.
Verify metrics in Offbeat
Apply the updated configuration and wait for the next metrics export. In the same Offbeat project, open Metrics → Explorer, select a metric your Collector sends, and use a time range that includes the export. If you see no new data, check the Collector logs for errors from the Offbeat exporter.
Test the ingest endpoint directly
To check connectivity and authentication independently of the Collector, set OFFBEAT_INGEST_KEY in your shell and send a test gauge. To confirm the point is queryable, look for queue.depth in Explorer.
curl -i -X POST https://ingest.offbeat.sh/v1/metrics \
-H "Authorization: Bearer $OFFBEAT_INGEST_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<JSON
{
"resourceMetrics": [{"scopeMetrics": [{"metrics": [{
"name": "queue.depth",
"gauge": {"dataPoints": [
{"timeUnixNano": "$(date +%s)000000000", "asInt": "1207"}
]}
}]}]}]
}
JSONTroubleshoot ingestion
Offbeat returns HTTP 200 after buffering accepted points. For an OTLP/JSON request with no rejected points, the response is{"partialSuccess":null}.
A response with partialSuccess can also have HTTP status200. Check rejectedDataPoints anderrorMessage for the rejection count and reasons.
{"partialSuccess":{"rejectedDataPoints":1,
"errorMessage":"1 data point rejected: 1 with no value (queue.depth)"}}HTTP errors
400- Invalid gzip or OTLP metrics payload. Check the encoding and payload format.
401- Missing or unrecognized ingest key. Check the bearer token. If you just created the key, wait a few seconds and retry.
413- The authenticated request body exceeds 4 MiB on the wire or after decompression. Send smaller batches.
415- Unsupported content type or encoding. Use
application/x-protobuforapplication/json. SetContent-Encodingtogzipfor compressed requests and omit it for uncompressed requests. 503- Ingest is temporarily unavailable. Retry the batch.
501- Offbeat accepts metrics at
/v1/metrics./v1/tracesand/v1/logsreturn this status after the ingest key and request body size checks pass.