by Cloud Foundry Authors

Adds an OpenTelemetry Collector to all Linux VMs to egress metrics and traces.

• Application integration

  Component

by Heroku Telemetry

Heroku Fir adds platform-native support for the collection and distribution of OpenTelemetry signals.

• Application integration

  Component

by Cisco ThousandEyes

It allows you to export ThousandEyes telemetry data in OTel format.

• Application integration

  Component

by ClickHouse Authors

ClickHouse creates trace spans for each query and some of the query execution stages, such as query planning or distributed queries.

• Application integration

  Component

by Envoy Proxy Authors

The OpenTelemetry tracing sandbox demonstrates Envoy’s request tracing capabilities using OpenTelemetry as the tracing provider.

• Application integration

  Component

by Duncan Po

MATLAB interface to OpenTelemetry.

• Application integration

  Component

by MySQL

MySQL Enterprise Edition generates OTel trace data on Linux platforms.

• Application integration

  Component

by Argo Workflows Authors

Argo Workflows provides native OpenTelemetry metrics to provide information from the workflow controller.

• Application integration

  Component

by Moby Project Authors

BuildKit supports OpenTelemetry.

• Application integration

  Component

by containerd Authors

containerd supports OpenTelemetry tracing since v1.6.0. Tracing currently targets only gRPC calls.

• Application integration

  Component

by cortex Authors

Cortex uses Jaeger or OpenTelemetry to implement distributed tracing

• Application integration

  Component

by CRI-O Authors

The crio.tracing table containers settings pertaining to the export of OpenTelemetry trace data.

• Application integration

  Component

by Dapr Authors

Dapr directly writes traces using the OpenTelemetry (OTLP) protocol as the recommended method.

• Application integration

  Component

by Docker Inc

buildx supports OpenTelemetry.

• Application integration

  Component

by Flipt Authors

Flipt supports distributed tracing via the OpenTelemetry project.

• Application integration

  Component

by Harbor Authors

Harbor can provide distributed tracing data for operators and administrator to know the current running status and to help troubleshooting

• Application integration

  Component

by Istio Authors

Make your application participate in tracing with OpenTelemetry, regardless of the language, framework, or platform you use to build your application.

• Application integration

  Component

by Jaeger Authors

Jaeger has the ability to trace some of its own components, namely the requests to the Query service.

• Application integration

  Component

by KEDA Authors

The KEDA Operator supports outputting metrics to the OpenTelemetry Collector using HTTP.

• Application integration

  Component

by Knative Authors

Analyze and understand the performance and behavior of Knative components

• Application integration

  Component

by Kong

Kong Mesh provides integration with OpenTelemetry.

• Application integration

  Component

by KrakenD Authors

The telemetry/opentelemetry component in KrakenD collects the activity generated for the enabled layers and pushes or exposes the data for pulling.

• Instrumentation

  Component

by Kubernetes Authors

System component traces record the latency of and relationships between operations in the cluster.

• Application integration

  Component

by Kuma Authors

Kuma provides integration with OpenTelemetry

• Application integration

  Component

by Kyverno Authors

Kyverno integrates OpenTelemetry.

• Application integration

  Component

by Open Policy Agent Authors

OPA will emit spans to an OpenTelemetry Collector via gRPC.

• Application integration

  Component

by OpenFeature Authors

flagd provides telemetry data out of the box. This telemetry data is compatible with OpenTelemetry.

• Application integration

  Component

by Otterize

OpenTelemetry support for network mapper.

• Application integration

  Component

by Spiral Scout

RoadRunner offers OTel (OpenTelemetry) plugin, which provides a unified standard for tracing, logging, and metrics information.

• Application integration

  Component

by Thanos Authors

Thanos supports exporting traces in the OpenTelemetry Protocol (OTLP)

• Application integration

  Component

by Traefik Labs

Traefik Hub uses OpenTelemetry to get insights into system performance and behavior.

• Application integration

  Component

by Tyk Technologies

You can leverage the power of OpenTelemetry to enhance your API monitoring with end-to-end distributed tracing.

• Application integration

  Component

by Keycloak Contributors

Keycloak utilizes OpenTelemetry for distributed tracing provided by the Quarkus OpenTelemetry extension.

• Application integration

  Component

by Microcks Authors

The main webapp component supports OpenTelemetry instrumentation for logs, distributed tracing and metrics.

• Application integration

  Component

by Strimzi Authors

In Strimzi, tracing facilitates the end-to-end tracking of messages: from source systems to Kafka, and then from Kafka to target systems and applications.

• Application integration

  Component

by Kong

• Application integration

  Component

by OpenFGA Authors

OpenFGA traces can be collected with the OTLP data format.

• Application integration

  Component

by APIContext

Send data from APIContext to any platform that intakes OpenTelemetry with our OpenTelemetry Webhook

• Application integration

  Component

by Checkmk GmbH

With this integration we introduced a new way for the developers to look deeper into what happens inside Checkmk through the use of OpenTelemetry traces, so that everyone using Checkmk could enjoy monitoring their infrastructure with a tool with the best performance and fewer bottlenecks.

• Application integration

  Component

by Cisco

The NSO Observability Exporter supports export of progress traces using OTLP.

• Application integration

  Component

by CsvPath Authors

CsvPath Framework uses OTLP to monitor delimited data preboarding jobs wherever they run, regardless of platform, namespace, project, or user.

• Application integration

  Component

• GNU Lesser General Public License v2.1

  License

by MLflow Authors

The MLflow tracing feature is built using OpenTelemetry, and allows users to trace the execution of their generative AI applications.

• Application integration

  Component

by Fluent CI

FluentCI Engine supports OpenTelemetry tracing.

• Application integration

  Component

by Kubewarden Authors

Kubewarden’s components are instrumented with the OpenTelemetry SDK, reporting data to an OpenTelemetry Collector.

• Application integration

  Component

by The Rust Project Developers

The feature otel can be used when building rustup to turn on OpenTelemetry tracing with an OTLP gRPC exporter.

• Application integration

  Component

• Apache-2.0 OR MIT

  License

by 🔭 OpenTelemetry Authors 🔭

Collector Supervisor for OpAMP

When building a custom collector you can add this utilities to the manifest file like the following:

utilities:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/cmd/opampsupervisor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Environment variable provider for OpenTelemetry Collector configuration maps.

When building a custom collector you can add this provider to the manifest file like the following:

providers:
    - gomod:
        go.opentelemetry.io/collector/confmap/provider/envprovider v1.38.0

by 🔭 OpenTelemetry Authors 🔭

File provider for OpenTelemetry Collector configuration maps.

When building a custom collector you can add this provider to the manifest file like the following:

providers:
    - gomod:
        go.opentelemetry.io/collector/confmap/provider/fileprovider v1.38.0

by 🔭 OpenTelemetry Authors 🔭

Google Secret Manager provider for OpenTelemetry Collector configuration maps.

When building a custom collector you can add this provider to the manifest file like the following:

providers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/confmap/provider/googlesecretmanagerprovider v0.132.0

by 🔭 OpenTelemetry Authors 🔭

HTTP provider for OpenTelemetry Collector configuration maps.

When building a custom collector you can add this provider to the manifest file like the following:

providers:
    - gomod:
        go.opentelemetry.io/collector/confmap/provider/httpprovider v1.38.0

by 🔭 OpenTelemetry Authors 🔭

HTTPS provider for OpenTelemetry Collector configuration maps.

When building a custom collector you can add this provider to the manifest file like the following:

providers:
    - gomod:
        go.opentelemetry.io/collector/confmap/provider/httpsprovider v1.38.0

by 🔭 OpenTelemetry Authors 🔭

YAML provider for OpenTelemetry Collector configuration maps.

When building a custom collector you can add this provider to the manifest file like the following:

providers:
    - gomod:
        go.opentelemetry.io/collector/confmap/provider/yamlprovider v1.38.0

by 🔭 OpenTelemetry Authors 🔭

Exports OTel Events (SpanEvent in Tracing added by AddEvent API) as Alerts to

backend to notify Errors or Change events.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/alertmanagerexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Alibaba Cloud Log Service Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/alibabacloudlogserviceexporter v0.132.0

by Cisco

Exports traces and/or metrics via HTTP to an APIClarity endpoint for analysis.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/openclarity/apiclarity/plugins/otel-collector/apiclarityexporter v0.0.0

by 🔭 OpenTelemetry Authors 🔭

The AWS X-Ray Tracing Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/awsxrayexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

AWS CloudWatch Logs Exporter sends logs data to AWS CloudWatch Logs

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/awscloudwatchlogsexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The AWS CloudWatch EMF Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/awsemfexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This exporter targets to support proto/JSON and proto/binary format

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/awss3exporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Azure Monitor Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/azuremonitorexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This exporter supports sending traces, metrics, and logs data to [Azure Blob storage] (https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview).

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/azureblobexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This exporter sends metrics, logs and trace data to Azure Data Explorer

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/azuredataexplorerexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Carbon Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/carbonexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This exporter supports sending OpenTelemetry logs and traces to Cassandra

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/cassandraexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This exporter supports sending OpenTelemetry logs and spans to ClickHouse

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/clickhouseexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Coralogix Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/coralogixexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Datadog Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/datadogexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Dataset Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/datasetexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Exports data to the console via zap.Logger.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        go.opentelemetry.io/collector/exporter/debugexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This exporter supports sending traces, metrics, and logs data to

(version >= 2.1).

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/dorisexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This exporter supports sending OpenTelemetry logs to Elasticsearch

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/elasticsearchexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The OpenTelemetry Collector Exporter for Faro

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/faroexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The File Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/fileexporter v0.132.0

by Romain Dauby

The OpenTelemetry Collector Exporter for the Fluent Forward protocol

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/r0mdau/fluentforwardexporter v0.4.0

by Google

The Google Cloud Operations Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/googlecloudexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This exporter sends OTLP messages to a Google Cloud Pubsub topic.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/googlecloudpubsubexporter v0.132.0

by Google

This exporter can be used to send metrics and traces to Google Cloud Managed Service for Prometheus.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/googlemanagedprometheusexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This exporter allows creating markers, via the Honeycomb Markers API, based on the look of incoming telemetry.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/honeycombmarkerexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This exporter supports sending tracing, metrics, and logging data to InfluxDB

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/influxdbexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Kafka Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/kafkaexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The schema name otel is an example. The user may change this to another name but the same name has to be used

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/kineticaexporter v0.130.0

by 🔭 OpenTelemetry Authors 🔭

The Trace ID aware load-balancing for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/loadbalancingexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This exporter supports sending logs and traces data to Logicmonitor

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/logicmonitorexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The OpenTelemetry Collector Exporter for Logz.io

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/logzioexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The OpenTelemetry Collector Exporter for Loki

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/lokiexporter v0.130.0

by 🔭 OpenTelemetry Authors 🔭

This exporter supports sending OpenTelemetry log data to Mezmo.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/mezmoexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Serves as a placeholder exporter in a pipeline. This can be useful if you want to e.g. start a Collector with only extensions enabled, or for testing Collector pipeline throughput without worrying about an exporter.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        go.opentelemetry.io/collector/exporter/nopexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The OpenCensus Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/opencensusexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

OpenSearch exporter supports sending OpenTelemetry signals as documents to OpenSearch.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/opensearchexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Exports telemetry data using

components with support for both OpenTelemetry Protocol with Apache Arrow and standard OpenTelemetry Protocol (OTLP) protocol via gRPC.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/otelarrowexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The OTLP gRPC Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        go.opentelemetry.io/collector/exporter/otlpexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Prometheus Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Prometheus Remote Write Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusremotewriteexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Pulsar exporter exports logs, metrics, and traces to Pulsar. This exporter uses a synchronous producer

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/pulsarexporter v0.132.0

by lorenzo@qxip.net, akvlad@qxip.net

This exporter supports sending OpenTelemetry logs, traces and metrics to ClickHouse using the qryn polyglot format.

by 🔭 OpenTelemetry Authors 🔭

Exports metrics, traces, and logs to RabbitMQ using the AMQP 0.9.1 protocol

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/rabbitmqexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The SAPM exporter builds on the Jaeger proto and adds additional batching on top. This allows

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sapmexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Sentry Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The SignalFx Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/signalfxexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Splunk HTTP Event Collector (HEC) Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/splunkhecexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Splunk SAPM Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sapmexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The OpenTelemetry Collector Exporter for Sumo Logic

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sumologicexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The syslog exporter supports sending messages to a remote syslog server.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/syslogexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This exporter supports sending OpenTelemetry log data to LogService.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/tencentcloudlogserviceexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Zipkin Exporter for the OpenTelemetry Collector.

When building a custom collector you can add this exporter to the manifest file like the following:

exporters:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/exporter/zipkinexporter v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This extension allows acking of data upon successful processing. The upstream agent can choose to send event again if ack fails.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/ackextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This extension provides Atlassian Service Authentication Protocol (ASAP) client credentials for HTTP or gRPC based exporters.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/asapauthextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This extension implements both configauth.ServerAuthenticator and configauth.ClientAuthenticator to authenticate clients and servers using Basic Authentication.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/basicauthextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Bearer token authenticator extension allows gRPC and HTTP-based exporters to add authentication data to outgoing calls based on a static token.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Datadog Extension for the OpenTelemetry Collector.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/datadogextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The encoding extension allows for other components to reference ingress/egress data formats

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/encoding v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This extension provides Google OAuth2 Client Credentials and Metadata for gRPC and HTTP based exporters.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/googleclientauthextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The headers_setter extension implements ClientAuthenticator and is used to set requests headers in gRPC / HTTP exporters with values provided via extension configurations or requests metadata (context).

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/headerssetterextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Health Check Extension for the OpenTelemetry Collector enables an HTTP URL that can be probed to check the status of the OpenTelemetry Collector.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/healthcheckextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This is an experimental extension that is intended to replace the existing health check extension.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/healthcheckv2extension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The HTTP Forwarder Extension for the OpenTelemetry Collector accepts HTTP requests, optionally adds headers to them and forwards them.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/httpforwarderextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This extension allows serving sampling strategies following the Jaeger’s remote sampling API.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/jaegerremotesampling v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The memory limiter extension is used to prevent out of memory situations on

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        go.opentelemetry.io/collector/extension/memorylimiterextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The OAuth2 Client Credentials authenticator extension allows gRPC and HTTP-based exporters to add authentication data to outgoing calls.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/oauth2clientauthextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Observers are implemented as an extension to discover networked endpoints like a Kubernetes pod, Docker container, or local listening port. Currently available are observers for docker, ecs, ecs_task, host and K8s.

by 🔭 OpenTelemetry Authors 🔭

The OIDC authenticator extension allows gRPC and HTTP-based receivers to require authentication from remote clients.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/oidcauthextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Collector extension for OpAMP

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/opampextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Performance Profiler Extension for the OpenTelemetry Collector can be used to collect performance profiles and investigate issues with the service.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/pprofextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This extension runs as a Web server that loads the remote observers that are registered against it.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/remotetapextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This extension provides SigV4 authentication for making requests to AWS services.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/sigv4authextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Solarwinds APM Settings extension gets Solarwinds APM specific settings from Solarwinds APM collector and /tmp/solarwinds-apm-settings.json & /tmp/solarwinds-apm-settings-raw periodically.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/solarwindsapmsettingsextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This extension is to be used in conjunction with the Sumo Logic Exporter in order to export telemetry data to Sumo Logic.

When building a custom collector you can add this extension to the manifest file like the following:

extensions:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/extension/sumologicextension v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The zPages Extension for the OpenTelemetry Collector serves zPages, an HTTP endpoint that provides live data for debugging different components that were properly instrumented for such.

by 🔭 OpenTelemetry Authors 🔭

The Attribute Processor for the OpenTelemetry Collector modifies attributes of a span.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/attributesprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Batch Processor for the OpenTelemetry Collector accepts spans, metrics, or logs and places them into batches.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        go.opentelemetry.io/collector/processor/batchprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Coralogix processor adds attributes to spans that enable features in Coralogix.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/coralogixprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The cumulative to delta processor converts monotonic, cumulative sum and histogram metrics to monotonic, delta metrics. Non-monotonic sums and exponential histograms are excluded.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/cumulativetodeltaprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The delta to cumulative processor (deltatocumulativeprocessor) converts metrics from delta temporality to cumulative, by accumulating samples in memory.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/deltatocumulativeprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The delta to rate processor converts delta sum metrics to rate metrics. This rate is a gauge.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/deltatorateprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Filter Processor for the OpenTelemetry Collector can be configured to include or exclude metrics.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The geoIP processor

enhances resource attributes by appending information about the geographical location of an IP address. To add geographical information, the IP address must be included in the resource attributes using the

.

by 🔭 OpenTelemetry Authors 🔭

The Group by Trace Processor for the OpenTelemetry Collector collects all the spans from the same trace, waiting a pre-determined amount of time before releasing the trace to the next processor.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/groupbytraceprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This processor re-associates spans, log records and metric data points to a Resource that matches with the specified attributes. As a result, all spans, log records or metric data points with the same values for the specified attributes are “grouped” under the same Resource.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/groupbyattrsprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The interval processor (intervalprocessor) aggregates metrics and periodically forwards the latest values to the next component in the pipeline.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/intervalprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The K8s Attribute Processor for the OpenTelemetry Collector automatically discovers K8s resources (pods), extracts metadata from them and adds the extracted metadata to the relevant spans, metrics and logs.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/k8sattributesprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This processor is used to deduplicate logs by detecting identical logs over a range of time and emitting a single log with the count of logs that were deduplicated.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/logdedupprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The logs transform processor can be used to apply log operators to logs coming from any receiver. Please refer to config.go for the config spec.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/logstransformprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Memory Limiter Processor for the OpenTelemetry Collector is used to prevent out of memory situations on the collector.

by 🔭 OpenTelemetry Authors 🔭

The Metrics Transform Processor for the OpenTelemetry Collector can be used to rename metrics, and add, rename or delete label keys and values. It can also be used to perform aggregations on metrics across labels or label values.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/metricstransformprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The metrics generation processor can be used to create new metrics using existing metrics following a given rule. Currently it supports following two approaches for creating a new metric.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/metricsgenerationprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Probabilistic Sampling Processor for the OpenTelemetry Collector provides probabilistic sampling of traces.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/probabilisticsamplerprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This processor deletes span attributes that don’t match a list of allowed span

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/redactionprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The WebSocket processor, which can be positioned anywhere in a pipeline, allows

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/remotetapprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Resource Processor for the OpenTelemetry Collector can be used to apply changes on resource attributes.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/resourceprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Resource Detection Processor for the OpenTelemetry Collector can be used to detect resource information from the host, in a format that conforms to the OpenTelemetry resource semantic conventions, and append or override the resource value in telemetry data with this information.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/resourcedetectionprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Routing Processor for the OpenTelemetry Collector will read a header from the incoming HTTP request (gRPC or plain HTTP) and direct the trace information to specific exporters based on the attribute’s value.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/routingprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Schema Processor is used to convert existing telemetry data or signals to a version of the semantic convention defined as part of the configuration.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/schemaprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Span Processor for the OpenTelemetry Collector modifies either the span name or attributes of a span based on the span name.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/spanprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Sumo Logic processor modifies the metadata on logs, metrics and traces sent to Sumo Logic so that the Sumo Logic apps can make full use of the ingested data.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/sumologicprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Tail Sampling Processor for the OpenTelemetry Collector samples traces based on a set of defined policies.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/tailsamplingprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Transform Processor for the OpenTelemetry Collector can be used to transform any fields on traces, metrics, and logs within the collector. It utilizes a transformation language to define transformations and conditions and then applies those transformations to the specified telemetry.

When building a custom collector you can add this processor to the manifest file like the following:

processors:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/processor/transformprocessor v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The active_directory_ds receiver scrapes metric relating to an Active Directory domain controller using the Windows Performance Counters.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/activedirectorydsreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Aerospike receiver is designed to collect performance metrics from one or more Aerospike nodes.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/aerospikereceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver fetches stats from a Apache Web Server instance using the server-status?auto endpoint.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/apachereceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver fetches metrics for an Apache Spark cluster through the Apache Spark REST API

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/apachesparkreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The AWS ECS Container Metrics Receiver for the OpenTelemetry Collector reads task metadata and docker stats from Amazon ECS Task Metadata Endpoint, and generates resource usage metrics (such as CPU, memory, network, and disk) from them.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awsecscontainermetricsreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The AWS X-Ray Receiver for the OpenTelemetry Collector accepts segments (i.e. spans) in the X-Ray Segment format. This enables the collector to receive spans emitted by the existing X-Ray SDK.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awsxrayreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Receives Cloudwatch events from AWS CloudWatch via the AWS SDK for Cloudwatch Logs

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awscloudwatchreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Receives Cloudwatch metrics from AWS Cloudwatch via the AWS SDK for Cloudwatch Logs

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awscloudwatchmetricsreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

AWS Container Insights Receiver is an AWS specific receiver that supports CloudWatch Container Insights.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awscontainerinsightreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Receiver for ingesting AWS Kinesis Data Firehose delivery stream messages and parsing the records received based on the configured record type.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awsfirehosereceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Receiver for retrieving trace previously stored in S3 by the AWS S3 Exporter.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awss3receiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver reads logs and trace data from Azure Blob Storage

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/azureblobreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Azure Event Hub receiver listens to logs emitted by Azure Event hubs.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/azureeventhubreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver scrapes Azure Monitor API for resources metrics.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/azuremonitorreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver fetches stats from a F5 Big-IP node using F5’s iControl REST API

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/bigipreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Carbon Receiver for the OpenTelemetry Collector supports Carbon’s plaintext protocol.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/carbonreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The chrony receiver is a pure go implementation of the command chronyc tracking

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/chronyreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This Cloudflare receiver allows Cloudflare’s LogPush Jobs to send logs from the Cloudflare logs aggregation system

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/cloudflarereceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Cloud Foundry receiver connects to the RLP (Reverse Log Proxy) Gateway of the Cloud Foundry installation

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/cloudfoundryreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The CollectD Receiver for the OpenTelemetry Collector can receive data exported by the CollectD’s write_http plugin.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/collectdreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver fetches stats from a CouchDB server.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/couchdbreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Datadog APM Receiver accepts traces in the Datadog APM format

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/datadogreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Docker Stats Receiver queries the local Docker daemon’s container stats API for all desired running containers on a configured interval.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/dockerstatsreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver queries the Elasticsearch node stats and index statsendpoints in order to scrape metrics from a running elasticsearch cluster.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/elasticsearchreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

An Expvar Receiver scrapes metrics from expvar

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/expvarreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The OpenTelemetry Collector Receiver for Faro

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/faroreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Filelog Receiver tails and parses logs from files using the opentelemetry-log-collection library.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/filelogreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The File Stats receiver collects metrics from files specified with a glob pattern.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/filestatsreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver uses Flink’s REST API to collect Jobmanager, Taskmanager, Job, Task and Operator metrics.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/flinkmetricsreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Fluent Forward Receiver for the OpenTelemetry Collector.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/fluentforwardreceiver v0.132.0

by Jeff Hostetler

A receiver for git Trace2 telemetry from local git commands, translates it into an OpenTelemetry format, and forwards it to other OpenTelemetry components.

by 🔭 OpenTelemetry Authors 🔭

The GitHub receiver receives data from

. As a starting point it scrapes metrics from repositories but will be extended to include traces and logs.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/githubreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The primary objective of the Google Cloud Monitoring Receiver is to gather time series metrics data from all Google services and convert this data into a pipeline format that facilitates further use.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/googlecloudmonitoringreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver gets OTLP messages from a Google Cloud Pubsub subscription.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/googlecloudpubsubreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Google Cloud Spanner enable you to investigate issues with your database

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/googlecloudspannerreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The HAProxy receiver generates metrics by polling periodically the HAProxy process through a dedicated socket or HTTP URL.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/haproxyreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Host Metrics Receiver for the OpenTelemetry Collector.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/hostmetricsreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The HTTP Check Receiver can be used for synthetic checks against HTTP endpoints. This receiver will make a request to the specified endpoint using the

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/httpcheckreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The iis receiver grabs metrics about an IIS instance using the Windows Performance Counters.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/iisreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver accepts metrics data as InfluxDB Line Protocol.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/influxdbreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Jaeger Receiver for the OpenTelemetry Collector.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/jaegerreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The JMX Receiver will work in conjunction with the OpenTelemetry JMX Metric Gatherer to report metrics from a target MBean server using a built-in or your custom OpenTelemetry helper-utilizing Groovy script.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/jmxreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Parses Journald events from systemd journal.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/journaldreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Kubernetes Cluster Receiver for the OpenTelemetry Collector collects cluster-level metrics from the Kubernetes API server. It uses the K8s API to listen for updates. A single instance of this receiver can be used to monitor a cluster.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sclusterreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Kubernetes Events receiver collects events from the Kubernetes

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8seventsreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Kubernetes Objects receiver collects(pull/watch) objects from the Kubernetes API server.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sobjectsreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Kafka Receiver for the OpenTelemetry Collector.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/kafkareceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Kafka metrics receiver collects Kafka metrics (brokers, topics, partitions, consumer groups) from Kafka server,

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/kafkametricsreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Kubelet Stats Receiver for the OpenTelemetry Collector pulls pod metrics from the API server on a kubelet and sends it down the metric pipeline for further processing.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/kubeletstatsreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Loki receiver implements the Loki Push API

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/lokireceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Memcached Receiver for the OpenTelemetry Collector can fetch stats from a Memcached instance using the stats command.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/memcachedreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver fetches stats from a MongoDB instance using the [golang

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/mongodbreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Receives metrics from MongoDB Atlas

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/mongodbatlasreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver queries MySQL’s global status and InnoDB tables.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/mysqlreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver supports opening a Unix Named Pipe (aka FIFO), and reading logs from it.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/namedpipereceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The NGINX Receiver for the OpenTelemetry Collector can fetch stats from a NGINX instance using a mod_status endpoint.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/nginxreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Serves as a placeholder receiver in a pipeline. This can be useful if you want to e.g. start a Collector with only extensions enabled.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        go.opentelemetry.io/collector/receiver/nopreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver fetches metrics important to run virtual networking using NSX-T. The receiver ingests metrics via the NSX Rest API

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/nsxtreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver periodically retrieves the clock offset from a NTP server.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/ntpreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The OpenCensus Receiver for the OpenTelemetry Collector.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/opencensusreceiver v0.132.0

by IBM Instana

OTel based Data Collector for LLM is the tool or template to generate OpenTelemetry metrics for various LLM and LLM Applications. All implementation are based on predefined OpenTelemetry Semantic Conventions.

by 🔭 OpenTelemetry Authors 🔭

This receiver collects metrics from an Oracle Database.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/oracledbreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The osquery receiver runs queries run on an

’s daemon on a schedule and converts the output to logs.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/osqueryreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Receives telemetry data using OpenTelemetry Protocol with Apache Arrow and standard OTLP protocol via gRPC.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/otelarrowreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The OTLP Receiver for the OpenTelemetry Collector.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        go.opentelemetry.io/collector/receiver/otlpreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver will read pipeline data from JSON files. The data is written in

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/otlpjsonfilereceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Podman Stats receiver queries the Podman service API to fetch stats for all running containers

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/podmanreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver queries the PostgreSQL statistics collector.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/postgresqlreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Prometheus Receiver for the OpenTelemetry Collector.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/prometheusreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/prometheusremotewritereceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Pulsar receiver receives logs, metrics, and traces from Pulsar.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/pulsarreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Pure Storage FlashArray receiver, receives metrics from Pure Storage internal services hosts.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/purefareceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Pure Storage FlashBlade receiver, receives metrics from Pure Storage FlashBlade via the Pure Storage FlashBlade OpenMetrics Exporter.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/purefbreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver fetches stats from a RabbitMQ node using the RabbitMQ Management Plugin.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/rabbitmqreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Receiver Creator Receiver for the OpenTelemetry Collector can instantiate other receivers at runtime based on whether observed endpoints match a configured rule.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/receivercreator v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Redis Receiver for the OpenTelemetry Collector is designed to retrieve Redis INFO data from a single Redis instance, build metrics from that data, and send them to the next consumer at a configurable interval.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/redisreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Riak metrics will be collected from the /stats endpoint.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/riakreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver can fetch stats from a SAP HANA instance. It leverages the driver written by SAP for connecting to SAP HANA with the golang SQL module to execute several monitoring queries.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/saphanareceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The SAPM Receiver for the OpenTelemetry Collector receive traces from other collectors or the SignalFx Smart Agent.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/sapmreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The SignalFx Receiver for the OpenTelemetry Collector accepts metrics in the SignalFx proto format and events (Logs) in the SignalFx proto format.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/signalfxreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Simple Prometheus Receiver for the OpenTelemetry Collector provides a simple configuration interface to configure the prometheus receiver to scrape metrics from a single target.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/simpleprometheusreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Receives trace data in Skywalking format.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/skywalkingreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver fetches stats from an SNMP-enabled host using the

. Metrics are collected based on configuration settings.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/snmpreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver collects metrics from a Snowflake account by connecting to an account and running queries at set intervals.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/snowflakereceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Solace receiver receives trace data from a Solace PubSub+ Event Broker

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/solacereceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Splunk HEC Receiver for the OpenTelemetry Collector accepts metrics, traces, and logs in the Splunk HEC format.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/splunkhecreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Splunk Enterprise Receiver is a pull based tool which enables the ingestion of performance metrics describing the operational status of a user’s Splunk Enterprise deployment to an appropriate observability tool.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/splunkenterprisereceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The SQL Query Receiver uses custom SQL queries to generate metrics from a database connection.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/sqlqueryreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The sqlserver receiver grabs metrics about a Microsoft SQL Server instance using the Windows Performance Counters.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/sqlserverreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver creates stats by connecting to an SSH server which may be an SFTP server.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/sshcheckreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The StatsD Receiver for the OpenTelemetry Collector ingests StatsD messages.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/statsdreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Parses Syslogs received over TCP or UDP.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/syslogreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/systemdreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Receives logs over TCP.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/tcplogreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Emit metrics about x.509 certificates.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/tlscheckreceiver v0.132.0

by Takuya Kajiwara

A receiver that generates synthetic traces based on a declarative blueprint for testing and demonstration purposes.

by 🔭 OpenTelemetry Authors 🔭

Receives logs over UDP.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/udplogreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This receiver fetches metrics from a vCenter or ESXi host running VMware vSphere APIs.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/vcenterreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Wavefront Receiver for the OpenTelemetry Collector.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/wavefrontreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Webhook Event receiver is meant to act as a generally available push based receiver for any webhook style data source.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/webhookeventreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Windows Performance Counters Receiver for the OpenTelemetry Collector captures the configured system, application, or custom performance counter data from the Windows registry using the PDH interface.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/windowsperfcountersreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

Tails and parses logs from windows event log API using the opentelemetry-log-collection library.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/windowseventlogreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Zipkin Receiver for the OpenTelemetry Collector.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/zipkinreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

The Zookeeper Receiver for the OpenTelemetry Collector collects metrics from a Zookeeper instance, using the ‘mntr’ command.

When building a custom collector you can add this receiver to the manifest file like the following:

receivers:
    - gomod:
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/zookeeperreceiver v0.132.0

by 🔭 OpenTelemetry Authors 🔭

This library allows to export data to the OpenTelemetry Collector using the OpenTelemetry Protocol.

by Microsoft Authors

The OpenTelemetry Azure Monitor Exporter for .NET

To install this exporter run:

dotnet add package Azure.Monitor.OpenTelemetry.Exporter

by 🔭 OpenTelemetry Authors 🔭

The console exporter prints data to the Console window.

To install this exporter run:

dotnet add package OpenTelemetry.Exporter.Console

by 🔭 OpenTelemetry Authors 🔭

The Geneva Exporter exports telemetry to Event Tracing for Windows (ETW) or to a Unix Domain Socket (UDS) on the local machine.

To install this exporter run:

dotnet add package OpenTelemetry.Exporter.Geneva

by 🔭 OpenTelemetry Authors 🔭

The InfluxDB exporter converts OpenTelemetry metrics into the InfluxDB model

To install this exporter run:

dotnet add package OpenTelemetry.Exporter.InfluxDB

by 🔭 OpenTelemetry Authors 🔭

The in-memory exporter stores data in a user provided memory buffer.

To install this exporter run:

dotnet add package OpenTelemetry.Exporter.InMemory

by 🔭 OpenTelemetry Authors 🔭

The Instana Exporter exports telemetry to Instana backend.

To install this exporter run:

dotnet add package OpenTelemetry.Exporter.Instana

by 🔭 OpenTelemetry Authors 🔭

The OneCollectorExporter is designed for Microsoft products to send data to public-facing end-points which route to Microsoft’s internal data pipeline.

To install this exporter run:

dotnet add package OpenTelemetry.Exporter.OneCollector

by 🔭 OpenTelemetry Authors 🔭

This library allows exporting telemetry data in the OpenTelemetry Protocol (OTLP) format to the OpenTelemetry Collector and OTLP-compliant backends/receivers.

To install this exporter run:

dotnet add package OpenTelemetry.Exporter.OpenTelemetryProtocol

by Chet Husk

A ready-to-use .NET CLR Startup Hook for applications that are instrumented with System.Diagnostic.Activity tracing that sends traces to an OpenTelemetry Collector via the OTLP Exporter without adding direct references to the OpenTelemetry SDK.

by 🔭 OpenTelemetry Authors 🔭

An OpenTelemetry Prometheus exporter for configuring an ASP.NET Core application with an endpoint for Prometheus to scrape.

To install this exporter run:

dotnet add package OpenTelemetry.Exporter.Prometheus.AspNetCore

by 🔭 OpenTelemetry Authors 🔭

An OpenTelemetry Prometheus exporter that configures an HttpListener instance for Prometheus to scrape.

To install this exporter run:

dotnet add package OpenTelemetry.Exporter.Prometheus.HttpListener

by 🔭 OpenTelemetry Authors 🔭

Stackdriver Exporter for OpenTelemetry .NET

To install this exporter run:

dotnet add package OpenTelemetry.Exporter.Stackdriver

by 🔭 OpenTelemetry Authors 🔭

Zipkin Exporter for OpenTelemetry .NET

To install this exporter run:

dotnet add package OpenTelemetry.Exporter.Zipkin

by 🔭 OpenTelemetry Authors 🔭

This library allows exporting telemetry data in the OpenTelemetry Protocol (OTLP) format to the OpenTelemetry Collector and OTLP-compliant backends/receivers.

by 🔭 OpenTelemetry Authors 🔭

This library provides a span exporter using the Zipkin protocol.

by Google Authors

The OpenTelemetry Google Cloud Monitoring Exporter for Go.

by Google Authors

The OpenTelemetry Google Cloud Trace Exporter for Go.

by Instana Authors

The Instana Go OpenTelemetry Exporter.

by Lightstep

The OpenTelemetry Lightstep Exporter for Go.

by 🔭 OpenTelemetry Authors 🔭

This library allows exporting telemetry data in the OpenTelemetry Protocol (OTLP) format to the OpenTelemetry Collector and OTLP-compliant backends/receivers.

by MrAlias

Provides a logr.Logger that exports messages as OTLP logs.

by Google

The OpenTelemetry Google Cloud Monitoring/Trace Exporters for Java.

by 🔭 OpenTelemetry Authors 🔭

This library allows exporting telemetry data in the OpenTelemetry Protocol (OTLP) format to the OpenTelemetry Collector and OTLP-compliant backends/receivers.

by 🔭 OpenTelemetry Authors 🔭

This library allows to export Prometheus data allowing Prometheus to query metric data.

by 🔭 OpenTelemetry Authors 🔭

This library allows to export data using the Zipkin Protocol.

by Microsoft Authors

The OpenTelemetry Azure Monitor Exporter for JavaScript (Node.js)

To install this exporter run:

npm install @azure/monitor-opentelemetry-exporter

by Google Authors

The OpenTelemetry Google Cloud Metric Exporter for Node.js.

To install this exporter run:

npm install @google-cloud/opentelemetry-cloud-monitoring-exporter

by Google Authors

The OpenTelemetry Google Cloud Trace Exporter for Node.js.

To install this exporter run:

npm install @google-cloud/opentelemetry-cloud-trace-exporter

by Instana Authors

The Instana Node.js OpenTelemetry Exporter.

To install this exporter run:

npm install @instana/opentelemetry-exporter

by 🔭 OpenTelemetry Authors 🔭

The OpenTelemetry Jaeger Exporter for Node.js.

To install this exporter run:

npm install @opentelemetry/exporter-jaeger

by 🔭 OpenTelemetry Authors 🔭

The OpenTelemetry Prometheus Exporter for Node.js.

To install this exporter run:

npm install @opentelemetry/exporter-prometheus

by Christian Dinse

OpenTelemetry exporter for SAP Cloud Logging is a Node.js package providing a set of auto-configured OpenTelemetry exporters for shipping logs, metrics and traces to SAP Cloud Logging.

To install this exporter run:

npm install @sap/opentelemetry-exporter-for-sap-cloud-logging

by 🔭 OpenTelemetry Authors 🔭

The OpenTelemetry Zipkin Exporter for Node.js.

To install this exporter run:

npm install @opentelemetry/exporter-zipkin

by jjatria

An unofficial implementation of the OTLP Exporter in Perl.

• Instrumentation

  Component

• Artistic-1.0-Perl

  License

by 🔭 OpenTelemetry Authors 🔭

This library allows exporting telemetry data in the OpenTelemetry Protocol (OTLP) over gRPC.

by 🔭 OpenTelemetry Authors 🔭

This library allows exporting telemetry data in the OpenTelemetry Protocol (OTLP) format to the OpenTelemetry Collector and OTLP-compliant backends/receivers.

To install this exporter run:

composer require open-telemetry/exporter-otlp

by 🔭 OpenTelemetry Authors 🔭

The OpenTelemetry Zipkin Exporter for PHP.

To install this exporter run:

composer require open-telemetry/exporter-zipkin

by Microsoft Authors

The OpenTelemetry Azure Monitor Exporter for Python

To install this exporter run:

pip install azure-monitor-opentelemetry-exporter

by Google

The OpenTelemetry Google Cloud Monitoring Exporters for Python.

by Google

The OpenTelemetry Google Cloud Trace Exporters for Python.

by Lightstep Authors

The OpenTelemetry Lightstep Exporter for Python.

by 🔭 OpenTelemetry Authors 🔭

This library allows to export traces and metrics using OpenCensus.

by 🔭 OpenTelemetry Authors 🔭

This library allows exporting telemetry data in the OpenTelemetry Protocol (OTLP) format to the OpenTelemetry Collector and OTLP-compliant backends/receivers.

by 🔭 OpenTelemetry Authors 🔭

This library allows to export data to the OpenTelemetry Collector using the OpenTelemetry Protocol using protobuf over gRPC.

by 🔭 OpenTelemetry Authors 🔭

This library allows to export data to the OpenTelemetry Collector using the OpenTelemetry Protocol using protobuf over HTTP.

by 🔭 OpenTelemetry Authors 🔭

This library allows to export metrics data to Prometheus.

by 🔭 OpenTelemetry Authors 🔭

This library allows export of tracing data to Zipkin using JSON for serialization.

by 🔭 OpenTelemetry Authors 🔭

This library allows export of tracing data to Zipkin using protobuf for serialization.

by Datadog, Inc.

Deprecated

This exporter has been deprecated. To export your OTLP traces from OpenTelemetry SDK directly to Datadog Agent, please refer to OTLP Ingest in Datadog Agent.

The OpenTelemetry Datadog Exporter for Ruby.

To install this exporter run:

gem install opentelemetry-exporters-datadog

by 🔭 OpenTelemetry Authors 🔭

The opentelemetry-exporter-jaeger gem provides a Jaeger exporter for OpenTelemetry Ruby

To install this exporter run:

gem install opentelemetry-exporter-jaeger

by 🔭 OpenTelemetry Authors 🔭

The opentelemetry-exporter-otlp gem provides an OTLP exporter for OpenTelemetry Ruby.

To install this exporter run:

gem install opentelemetry-exporter-otlp

by 🔭 OpenTelemetry Authors 🔭

The opentelemetry-exporter-otlp-grpc gem provides an OTLP exporter over gRPC for OpenTelemetry Ruby.

by 🔭 OpenTelemetry Authors 🔭

The opentelemetry-exporter-otlp-http gem provides an OTLP over HTTP exporter for OpenTelemetry Ruby.

by 🔭 OpenTelemetry Authors 🔭

The opentelemetry-exporter-otlp-metrics gem provides an OTLP metrics exporter for OpenTelemetry for Ruby.

by 🔭 OpenTelemetry Authors 🔭

The opentelemetry-exporter-zipkin gem provides a Zipkin exporter for OpenTelemetry Ruby.

To install this exporter run:

gem install opentelemetry-exporter-zipkin

by Jan Kuehle