Loading full navigation.

Autonomous IT is here. The alert loop ends now. LEARN MORE

Partners

Docs

LM Academy

LM Community

Pricing

Platform
Solution
Industry
Role
There is no result.
Try it free

14-day access to the full LogicMonitor platform

OpenTelemetry Metrics Overview

Last updated – 12 October, 2026

OpenTelemetry is an open-source, vendor-neutral observability framework for generating, collecting, and exporting telemetry data, including metrics, traces, and logs.

OpenTelemetry Metrics are runtime measurements that describe the health and performance of your applications and infrastructure over time. Examples include request counts, request latency, memory usage, and error rates.

The OpenTelemetry Metrics API records metric measurements, while the OpenTelemetry SDK aggregates and exports metric data to an OpenTelemetry Collector or an observability backend. This architecture supports portable instrumentation, reduces vendor lock-in, and provides metrics for dashboards, alerting, troubleshooting, and capacity planning
The following diagram illustrates the OpenTelemetry Metrics workflow:

OpenTelemetry Metrics workflow diagram

Key Components for OpenTelemetry Metrics

The OpenTelemetry Metrics workflow includes the following components:

  • Telemetry Sources—Metric data comes from applications, Kubernetes environments, cloud services, and infrastructure. Applications use the OpenTelemetry (OTel) SDK, Kubernetes environments and infrastructure use collectors or receivers, and cloud services use APIs or exporters.
  • OpenTelemetry Collector—Receivers collect metric data, processors process the data, and exporters send the processed data to the configured endpoint.
  • LogicMonitor OTLP Endpoint—The OTLP Metrics Ingestion Endpoint receives metrics over OTLP/HTTP for ingestion into the LogicMonitor platform.
  • LogicMonitor Platform—Dashboards visualize metrics, Alerts provides metric-based alerting, and Explore provides queries using PromQL-compatible expressions.

General Requirements for Using OpenTelemetry Metrics

To use OpenTelemetry Metrics, you need the following:

  • You must enable the OpenTelemetry Metrics feature flag before the feature is available in the LogicMonitor platform.
  • To ingest OTLP metrics into the LogicMonitor platform, you need a LogicMonitor user with the “Manage” permission for OpenTelemetry Metrics in the Settings role permissions.
  • To query OTLP metrics, you need “Read“ permission.

OpenTelemetry and Standard LogicMonitor Metrics Comparison

LogicMonitor supports both standard LogicMonitor metrics and OTLP metrics. Although both store time-series metric data, they differ in their data model, collection method, resource organization, and query capabilities.

FeatureStandard LogicMonitor MetricsOpenTelemetry Metrics
Data modelHierarchical model consisting of resources, DataSources, instances, and datapointsFlat metric model that identifies metrics by metric name and attributes
Collection modelLogicMonitor Collector polls monitored resources using supported collection protocolsOpenTelemetry Collector or SDK pushes metrics to the LogicMonitor OTLP endpoint
Metric identityLogicMonitor associates metrics with monitored resources and the Resource treeMetrics are identified by a metric name and a unique set of attributes
Resource registrationResources must exist in the Resource tree before LogicMonitor collects metricsYou do not need to register resources before LogicMonitor ingests metrics.
Metric discoveryDataSources define metrics, and Active Discovery discovers them.Metrics become available when the OpenTelemetry Collector or SDK sends them
OrganizationMetrics are organized through the Resource tree hierarchyYou can organize metrics dynamically using attributes at query time
Query languageLMQLPromQL-compatible expressions
AlertingYou configure thresholds on datapoints in the LogicMonitor resource hierarchyYou base alert rules on metric names, attribute filters, and PromQL-compatible expressions
Typical use casesUse standard LogicMonitor metrics when you collect metrics from traditional infrastructure by using LogicMonitor Collectors and DataSources.Use OpenTelemetry Metrics when your applications or infrastructure already produce OpenTelemetry telemetry, such as cloud-native applications and Kubernetes environments, or when you want to use streaming telemetry.