Option 1
OpenTelemetry
A vendor-neutral set of APIs, SDKs, conventions, and components for generating and collecting traces, metrics, and logs.
Side-by-side guides
OpenTelemetry provides vendor-neutral ways to instrument and export telemetry; Prometheus focuses on collecting, storing, and querying metrics.
Option 1
A vendor-neutral set of APIs, SDKs, conventions, and components for generating and collecting traces, metrics, and logs.
Option 2
A metrics monitoring system that collects and stores time-series data and supports PromQL queries and alerting.
| What to compare | OpenTelemetry | Prometheus |
|---|---|---|
| Primary role | Instrument software and provide a common pipeline for telemetry signals. | Collect, store, query, and alert on numeric time-series metrics. |
| Signals | Supports traces, metrics, and logs through its APIs and ecosystem. | Focuses on metrics; logs and traces typically come from complementary systems. |
| Data destination | An application or Collector exports telemetry to compatible backends; OpenTelemetry is not itself a permanent storage system. | Prometheus stores the metrics it collects and makes them available to queries and alerting rules. |
| How they fit | Can standardize instrumentation and route supported telemetry through compatible receivers and exporters. | Can serve as a metrics backend in an observability setup; verify the integration path and configuration for your versions. |
Teams that want consistent, portable instrumentation across services and more than one telemetry signal.
Teams that need a focused system for collecting, querying, and alerting on time-series metrics.