| Honeycomb | Honeycomb offers distributed tracing.[1] | Honeycomb supports OpenTelemetry.[1] [2] | Honeycomb offers log analytics.[1] | | Honeycomb lists SLOs and triggers among its capabilities.[1] [2] |
|---|
| Datadog | Datadog provides application performance monitoring.[3] | Datadog supports OpenTelemetry integrations.[3] | Datadog provides log management.[3] | Datadog monitors infrastructure and custom metrics.[3] | Datadog provides alerts and service level objectives.[3] |
|---|
| New Relic | New Relic includes application performance monitoring and distributed tracing.[4] | New Relic names OpenTelemetry, Prometheus, StatsD, and eBPF as open standards.[5] | New Relic correlates logs with applications and other telemetry.[5] | New Relic monitors hosts, Kubernetes, cloud integrations, and network performance.[4] | New Relic describes alerting grounded in telemetry and team knowledge.[4] |
|---|
| Elastic Observability | Elastic Observability monitors applications and backend telemetry.[6] | Elastic is OpenTelemetry-first and Prometheus-native.[7] | Elastic Observability includes log collection and exploration.[7] | Elastic Observability collects infrastructure data from hosts, containers, Kubernetes, and cloud services.[8] | Elastic Observability defines alert rules and SLOs.[9] [7] |
|---|
| Dash0 | Dash0 lists traces among its stored telemetry signals.[10] | Dash0 describes OpenTelemetry-native telemetry and names PromQL, Fluentd, Fluentbit, Logstash, and Vector.[10] [11] | Dash0 lists logs among its stored telemetry signals.[10] | Dash0 integrates cloud services and Kubernetes for monitoring.[11] | Dash0 provides alerting rules for monitoring.[11] |
|---|
| Dynatrace | Dynatrace captures code-level context for distributed traces end to end.[12] | Dynatrace pricing lists OpenTelemetry metrics and traces.[13] | Dynatrace correlates logs in context.[14] | Dynatrace monitors host health, processes, filesystems, and operating-system services.[14] | |
|---|
| groundcover | groundcover describes a full-stack observability platform.[15] | groundcover describes native support for OpenTelemetry and open standards.[15] | | groundcover monitors workloads running in the cloud.[15] | |
|---|
| Logz.io Observability Platform | Logz.io lists distributed tracing as part of its observability platform.[16] | Logz.io lists OpenTelemetry and Prometheus as supported technologies.[16] | Logz.io offers log management.[16] | Logz.io publishes an infrastructure monitoring offering.[17] | Logz.io lists alerting among its platform capabilities.[18] |
|---|
| Coralogix | Coralogix provides application performance monitoring and trace data.[19] | Coralogix ingests OpenTelemetry, AWS, Azure, GCP, and eBPF sources.[19] | Coralogix stores and queries logs in its telemetry lake.[19] | Coralogix collects infrastructure metrics.[19] | |
|---|
| SigNoz | SigNoz provides APM and trace monitoring.[20] | SigNoz Cloud is an OpenTelemetry-native platform.[20] | SigNoz provides log search with trace correlation.[20] | SigNoz monitors Kubernetes, hosts, and cloud metrics.[20] | SigNoz includes alerts across telemetry signals.[20] |
|---|
| Uptrace | Uptrace processes spans and provides application tracing.[21] | Uptrace identifies its observability platform as OpenTelemetry-native.[21] | Uptrace unifies traces, metrics, and logs in one platform.[21] | Uptrace includes infrastructure monitoring.[21] | |
|---|
| VictoriaMetrics Cloud | VictoriaMetrics Cloud includes VictoriaTraces.[22] | VictoriaMetrics Cloud accepts telemetry from named collectors and agents.[23] | VictoriaMetrics Cloud includes managed VictoriaLogs and full-text log queries.[22] | VictoriaMetrics Cloud provides managed VictoriaMetrics.[22] | |
|---|
| Better Stack | Better Stack provides eBPF-based, OpenTelemetry-native tracing.[24] | Better Stack identifies tracing and infrastructure monitoring as OpenTelemetry-native.[24] | Better Stack lists log management for collecting insights across a stack.[24] | Better Stack provides OpenTelemetry-native infrastructure monitoring.[24] | |
|---|
| IBM Instana Observability | Instana provides real-time full-stack data to trace and fix application issues.[25] | Instana lists OpenTelemetry as a supported capability.[25] | | Instana automatically instruments infrastructure and applications.[25] | |
|---|
| Splunk Observability Cloud | Splunk Observability Cloud correlates traces, metrics, and logs.[26] | | Splunk Observability Cloud correlates logs with metrics and traces.[26] | Splunk Observability Cloud monitors clouds, containers, and on-premises environments.[26] | |
|---|
| BugSnag | BugSnag traces requests across the application stack.[27] | | | | |
|---|
| Sentry | Sentry connects spans and metrics to traces and traces slow requests.[28] | | Sentry connects logs with errors, replays, spans, profiles, and metrics.[28] | | |
|---|
| Axiom | Axiom collects OpenTelemetry logs, metrics, and traces.[29] | Axiom collects OpenTelemetry logs, metrics, and traces.[29] | Axiom stores machine data in a managed, schema-less event store.[29] | | |
|---|
| Grafana Cloud | Grafana Cloud retains and provides access to traces.[30] | | Grafana Cloud retains logs alongside metrics and traces.[30] | Grafana Cloud provides Kubernetes monitoring.[30] | |
|---|
| Sumo Logic | Sumo Logic supports application observability and service troubleshooting.[31] | | Sumo Logic provides log management for cloud and application operations.[31] | Sumo Logic provides infrastructure monitoring.[31] | |
|---|