Vendors

Vendors who natively support OpenTelemetry

A non-exhaustive list of organizations offering solutions that consume OpenTelemetry natively via OTLP, such as observability backends and observability pipelines.

Some organizations provide a distribution (of customized OpenTelemetry components), that provides additional capabilities or for improved ease of use.

Organization1OSSCom­mer­cialDistri­butionNative OTLPLearn more
Apache SkyWalkingYesNoYes skywalking.apache.org/… 
Fluent BitYesNoYes docs.fluentbit.io/… 
JaegerYesNoYes www.jaegertracing.io/… 
ClickHouseYesYesNo github.com/… 
Grafana LabsYesYesYes grafana.com/… 
GreptimeDBYesYesYes docs.greptime.com/… 
HighlightYesYesYes www.highlight.io/… 
HyperDXYesYesYes www.hyperdx.io/… 
observIQYesYesYes docs.bindplane.observiq.com 
OneUptimeYesYesYes oneuptime.com/… 
OpenObserveYesYesYes openobserve.ai/… 
qrynYesYesYes qryn.metrico.in/… 
Red HatYesYesYes docs.openshift.com/… 
SigNozYesYesYes signoz.io 
TracetestYesYesYes docs.tracetest.io/… 
VictoriaMetricsYesYesYes github.com/… 
Alibaba CloudNoYesYes www.alibabacloud.com/… 
AppDynamics (Cisco)NoYesYes docs.appdynamics.com/… 
Aria by VMware (Wavefront)NoYesYes docs.wavefront.com/… 
AspectoNoYesYes www.aspecto.io 
AWSNoYesNo aws-otel.github.io 
AzureNoYesNo docs.microsoft.com/… 
Better StackNoYesYes betterstack.com/… 
CauselyNoYesYes github.com/… 
ChronosphereNoYesYes docs.chronosphere.io/… 
Control PlaneNoYesYes docs.controlplane.com/… 
CoralogixNoYesYes coralogix.com/… 
CriblNoYesYes docs.cribl.io/… 
DaoCloudNoYesYes docs.daocloud.io/… 
DatadogNoYesYes docs.datadoghq.com/… 
DynatraceNoYesYes www.dynatrace.com/… 
ElasticNoYesYes www.elastic.co/… 
F5NoYesYes github.com/… 
Google Cloud PlatformNoYesYes github.com/… 
HeliosNoYesYes gethelios.dev/… 
HoneycombNoYesYes docs.honeycomb.io/… 
Immersive FusionNoYesYes docs.immersivefusion.com/… 
InstanaNoYesYes www.ibm.com/… 
ITRSNoYesYes docs.itrsgroup.com/… 
KloudFuseNoYesYes kloudfuse.atlassian.net/… 
KloudMateNoYesYes docs.kloudmate.com/… 
LogicMonitorNoYesYes www.logicmonitor.com/… 
LogScale by Crowdstrike (Humio)NoYesYes library.humio.com/… 
Logz.ioNoYesNo docs.logz.io/… 
LumigoNoYesYes docs.lumigo.io/… 
MiddlewareNoYesYes docs.middleware.io/… 
New RelicNoYesYes newrelic.com/… 
Observe, Inc.NoYesYes docs.observeinc.com/… 
ObserveAnyNoYesYes www.observeany.com/… 
OpenTextNoYesYes docs.microfocus.com/… 
OracleNoYesYes docs.oracle.com/… 
SentryNoYesNo sentry.io/… 
Sentry SoftwareNoYesYes www.sentrysoftware.com/… 
SeqNoYesYes docs.datalust.co/… 
ServiceNow Cloud Observability (Lightstep)NoYesYes github.com/… 
ServicePilotNoYesYes www.servicepilot.com/… 
SolarWindsNoYesYes documentation.solarwinds.com/… 
SplunkNoYesYes docs.splunk.com/… 
Sumo LogicNoYesYes help.sumologic.com/… 
TelemetryHubNoYesYes app.telemetryhub.com/… 
TingYunNoYesYes wukongdoc.tingyun.com/… 
TraceloopNoYesYes www.traceloop.com 
UptraceNoYesYes uptrace.dev 
VuNet SystemsNoYesYes vunetsystems.com/… 

Add your organization

To have your organization listed, submit a PR with an entry added to the vendors list. The entry should include the following:

  • Link to the documentation that details how your offering consumes OpenTelemetry natively via OTLP.
  • Link to your distribution, if applicable
  • Link that proves that your offering is open source, if applicable. An open source distribution does not qualify your offering to be marked “open source”.
  • GitHub handle or email address as a point of contact so that we can reach out in case we have questions

Note that this list is for organizations that consume OpenTelemetry and offer Observability to end users.

If you adopt OpenTelemetry for Observability as an end-user organization, and you do not provide any kind of services around OpenTelemetry, see Adopters.

If you provide a library, service, or app that is made observable through OpenTelemetry, see Integrations.


  1. Organizations are grouped as follows based on their OTel support:

    • Pure OSS
    • Mixed OSS/commercial
    • Commercial
    • Alphabetical within each group
     ↩︎
Last modified March 14, 2024: Ecosystem policy updates (#4153) (04ed0d3c)