OTLP API Endpoints

Direct OTLP endpoint for OpenTelemetry exporters

Primary Endpoint

RocketLogs accepts OTLP data over HTTP. Use this endpoint for all telemetry types (traces, metrics, logs):

https://ingress.us-east-2.rocketgraph.app

Signal-Specific Paths

If your exporter requires specific paths for each signal type:

Traces

https://ingress.us-east-2.rocketgraph.app/v1/traces

Metrics

https://ingress.us-east-2.rocketgraph.app/v1/metrics

Logs

https://ingress.us-east-2.rocketgraph.app/v1/logs

Authentication

All requests must include a Bearer token in the Authorization header:

Authorization: Bearer YOUR_ROCKETLOGS_API_TOKEN

Get your API token from Settings.

Standard Environment Variables

Configure any OpenTelemetry SDK using these standard environment variables:

# Required
export OTEL_EXPORTER_OTLP_ENDPOINT="https://ingress.us-east-2.rocketgraph.app"
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer YOUR_ROCKETLOGS_API_TOKEN"

# Recommended
export OTEL_SERVICE_NAME="your-service-name"
export OTEL_METRICS_EXPORTER=otlp
export OTEL_LOGS_EXPORTER=otlp
export OTEL_TRACES_EXPORTER=otlp

Protocol Support

Supported

OTLP/HTTP (default)
OTLP/HTTP with protobuf
OTLP/HTTP with JSON

Coming Soon

OTLP/gRPC

Quick Test

Test your connection with a simple curl command:

curl -X POST https://ingress.us-east-2.rocketgraph.app/v1/traces \
  -H "Authorization: Bearer YOUR_ROCKETLOGS_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

A successful response will return HTTP 200.