| Datadog | Datadog monitors infrastructure and custom metrics.[1] | Datadog provides application performance monitoring.[1] | Datadog provides log management.[1] | Datadog supports OpenTelemetry integrations.[1] | Datadog monitors Amazon Web Services, Microsoft Azure, Google Cloud, and Kubernetes.[1] |
|---|
| New Relic | New Relic monitors hosts, Kubernetes, cloud integrations, and network performance.[2] | New Relic includes application performance monitoring and distributed tracing.[2] | New Relic correlates logs with applications and other telemetry.[3] | New Relic names OpenTelemetry, Prometheus, StatsD, and eBPF as open standards.[3] | New Relic names OpenTelemetry, Prometheus, StatsD, and eBPF telemetry inputs.[3] |
|---|
| Elastic Observability | Elastic Observability collects infrastructure data from hosts, containers, Kubernetes, and cloud services.[4] | Elastic Observability monitors applications and backend telemetry.[5] | Elastic Observability includes log collection and exploration.[6] | Elastic is OpenTelemetry-first and Prometheus-native.[6] | Elastic documents AWS, Kubernetes, and Slack integrations.[4] [6] |
|---|
| Dash0 | Dash0 integrates cloud services and Kubernetes for monitoring.[7] | Dash0 lists traces among its stored telemetry signals.[8] | Dash0 lists logs among its stored telemetry signals.[8] | Dash0 describes OpenTelemetry-native telemetry and names PromQL, Fluentd, Fluentbit, Logstash, and Vector.[8] [7] | Dash0 names Kubernetes, Vercel, and Amazon CloudWatch integrations.[7] |
|---|
| Dynatrace | Dynatrace monitors host health, processes, filesystems, and operating-system services.[9] | Dynatrace captures code-level context for distributed traces end to end.[10] | Dynatrace correlates logs in context.[9] | Dynatrace pricing lists OpenTelemetry metrics and traces.[11] | |
|---|
| groundcover | groundcover monitors workloads running in the cloud.[12] | groundcover describes a full-stack observability platform.[12] | | groundcover describes native support for OpenTelemetry and open standards.[12] | groundcover lists Amazon Web Services, Google Cloud Platform, and Microsoft Azure marketplaces.[13] |
|---|
| Logz.io Observability Platform | Logz.io publishes an infrastructure monitoring offering.[14] | Logz.io lists distributed tracing as part of its observability platform.[15] | Logz.io offers log management.[15] | Logz.io lists OpenTelemetry and Prometheus as supported technologies.[15] | Logz.io names AWS, OpenTelemetry, and Prometheus.[15] |
|---|
| Coralogix | Coralogix collects infrastructure metrics.[16] | Coralogix provides application performance monitoring and trace data.[16] | Coralogix stores and queries logs in its telemetry lake.[16] | Coralogix ingests OpenTelemetry, AWS, Azure, GCP, and eBPF sources.[16] | Coralogix integrates with AWS, Azure, GCP, Kubernetes, and Heroku.[16] |
|---|
| SigNoz | SigNoz monitors Kubernetes, hosts, and cloud metrics.[17] | SigNoz provides APM and trace monitoring.[17] | SigNoz provides log search with trace correlation.[17] | SigNoz Cloud is an OpenTelemetry-native platform.[17] | SigNoz names Kubernetes, OpenAI, Azure OpenAI, Gemini, OpenRouter, and LiteLLM.[17] |
|---|
| Uptrace | Uptrace includes infrastructure monitoring.[18] | Uptrace processes spans and provides application tracing.[18] | Uptrace unifies traces, metrics, and logs in one platform.[18] | Uptrace identifies its observability platform as OpenTelemetry-native.[18] | Uptrace is built on ClickHouse.[18] |
|---|
| VictoriaMetrics Cloud | VictoriaMetrics Cloud provides managed VictoriaMetrics.[19] | VictoriaMetrics Cloud includes VictoriaTraces.[19] | VictoriaMetrics Cloud includes managed VictoriaLogs and full-text log queries.[19] | VictoriaMetrics Cloud accepts telemetry from named collectors and agents.[20] | VictoriaMetrics Cloud deployments run on AWS and support AWS PrivateLink.[20] |
|---|
| Better Stack | Better Stack provides OpenTelemetry-native infrastructure monitoring.[21] | Better Stack provides eBPF-based, OpenTelemetry-native tracing.[21] | Better Stack lists log management for collecting insights across a stack.[21] | Better Stack identifies tracing and infrastructure monitoring as OpenTelemetry-native.[21] | |
|---|
| IBM Instana Observability | Instana automatically instruments infrastructure and applications.[22] | Instana provides real-time full-stack data to trace and fix application issues.[22] | | Instana lists OpenTelemetry as a supported capability.[22] | |
|---|
| Splunk Observability Cloud | Splunk Observability Cloud monitors clouds, containers, and on-premises environments.[23] | Splunk Observability Cloud correlates traces, metrics, and logs.[23] | Splunk Observability Cloud correlates logs with metrics and traces.[23] | | |
|---|
| Splunk AppDynamics | AppDynamics monitors cloud, container, and on-premises infrastructure.[24] | | | AppDynamics collects telemetry through agents and OpenTelemetry.[24] | Splunk AppDynamics offers SAP monitoring and tracks user journeys across APIs and third-party services.[25] |
|---|
| Pingdom | Pingdom monitors servers, virtual hosts, and containerized environments.[26] | | Pingdom provides hosted multi-source log management with search and analysis.[26] | | Pingdom integrates with AWS, Azure, Docker, and Kubernetes for infrastructure monitoring.[26] |
|---|
| Grafana Cloud | Grafana Cloud provides Kubernetes monitoring.[27] | Grafana Cloud retains and provides access to traces.[27] | Grafana Cloud retains logs alongside metrics and traces.[27] | | |
|---|
| Sumo Logic | Sumo Logic provides infrastructure monitoring.[28] | Sumo Logic supports application observability and service troubleshooting.[28] | Sumo Logic provides log management for cloud and application operations.[28] | | Sumo Logic lists AWS and Kubernetes monitoring.[28] |
|---|