Configure Prometheus OTLP ingestion endpoint to receive metrics from OTel SDK applications directly without a Collector
domain: prometheus.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Enable the OTLP receiver in Prometheus by adding --web.enable-otlp-receiver to the startup flags (Prometheus 2.47+)
Point the OTel SDK OTLP metrics exporter at the Prometheus OTLP endpoint POST /api/v1/otlp/v1/metrics with HTTP transport
Set the preferred_temporality in the SDK exporter to cumulative to match Prometheus's scrape model expectations
Verify ingested metrics appear in the Prometheus UI by querying the metric name with the service_name label derived from the OTel resource
Configure Prometheus scrape intervals and retention normally; OTLP-ingested metrics are stored identically to scraped metrics
Known gotchas
Prometheus converts OTel metric names by replacing dots with underscores and appending units; plan metric names with this transformation in mind to avoid collisions
Delta temporality metrics from some SDKs are not supported by the Prometheus OTLP endpoint; the endpoint rejects them with a 400 error requiring SDK reconfiguration
Resource attributes from the OTel SDK are converted to Prometheus labels; high-cardinality resource attributes such as host.id inflate time series count
Give your agent this knowledge — and 15,800+ more routes
One MCP install gives any agent live access to the full route map across 5,800+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?