Integration · APM & alerting
OpenTelemetry
OTLP ingestion: metrics + traces + logs.
What gets collected
OTLP/gRPC and OTLP/HTTP collector receivers. Metrics land in the TSDB; traces go to a Jaeger-compatible store (optional).
Requirements
- ✓OTLP/gRPC :4317
- ✓OTLP/HTTP :4318
- ✓OTel SDK or Collector
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
otlp.metrics.receivedotlp.traces.spansotlp.logs.recordsotlp.export.errorsSetup steps
- 1
otlp-receiver:4317 (gRPC) / :4318 (HTTP) - 2Point the OTel SDK in your app at the endpoint
After install
- · Metrics show up on the dashboard within 15-30 seconds
- · Integration labels flow into filters automatically
- · Dashboard presets for common metrics are available in the editor
More in the docs
OpenTelemetry
Frequently asked questions
- What does Unimoni collect from OpenTelemetry?
- OTLP ingestion: metrics + traces + logs. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across OpenTelemetry and everything else in one place.
- How long does it take to connect OpenTelemetry?
- Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
- What access does the OpenTelemetry integration need?
- Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
- Is OpenTelemetry monitoring available self-hosted and on the free plan?
- Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.