go: go.opentelemetry.io/otel

Package otel provides global access to the OpenTelemetry API. The subpackages of the otel package provide an implementation of the OpenTelemetry API. The provided API is used to instrument code and measure data about that code's performance and operation. The measured data, by default, is not processed or transmitted anywhere. An implementation of the OpenTelemetry SDK, like the default SDK implementation (go.opentelemetry.io/otel/sdk), and associated exporters are used to process and transport this data. To read the getting started guide, see https://opentelemetry.io/docs/languages/go/getting-started/. To read more about tracing, see go.opentelemetry.io/otel/trace. To read more about metrics, see go.opentelemetry.io/otel/metric. To read more about logs, see go.opentelemetry.io/otel/log. To read more about propagation, see go.opentelemetry.io/otel/propagation and go.opentelemetry.io/otel/baggage.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T04:01:54.121Z (about 1 month ago)
• Versions: 78
• Dependent Packages: 15,241
• Dependent Repositories: 29,020
• Docker Downloads: 45,341,687,593
• Rankings:
  • Docker downloads count: 0.01%
  • Dependent packages count: 0.015%
  • Dependent repos count: 0.035%
  • Average: 0.399%
  • Forks count: 0.899%
  • Stargazers count: 1.038%

go: go.opentelemetry.io/otel/sdk

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/sdk#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.32.0 (published about 1 month ago)
• Last Synced: 2024-11-13T12:30:51.212Z (about 1 month ago)
• Versions: 61
• Dependent Packages: 9,169
• Dependent Repositories: 21,744
• Docker Downloads: 34,928,750,889
• Rankings:
  • Docker downloads count: 0.012%
  • Dependent packages count: 0.027%
  • Dependent repos count: 0.044%
  • Average: 0.403%
  • Forks count: 0.896%
  • Stargazers count: 1.035%

go: go.opentelemetry.io/otel/metric

Package metric provides the OpenTelemetry API used to measure metrics about source code operation. This API is separate from its implementation so the instrumentation built from it is reusable. See go.opentelemetry.io/otel/sdk/metric for the official OpenTelemetry implementation of this API. All measurements made with this package are made via instruments. These instruments are created by a Meter which itself is created by a MeterProvider. Applications need to accept a MeterProvider implementation as a starting point when instrumenting. This can be done directly, or by using the OpenTelemetry global MeterProvider via GetMeterProvider. Using an appropriately named Meter from the accepted MeterProvider, instrumentation can then be built from the Meter's instruments. Each instrument is designed to make measurements of a particular type. Broadly, all instruments fall into two overlapping logical categories: asynchronous or synchronous, and int64 or float64. All synchronous instruments (Int64Counter, Int64UpDownCounter, Int64Histogram, Float64Counter, Float64UpDownCounter, and Float64Histogram) are used to measure the operation and performance of source code during the source code execution. These instruments only make measurements when the source code they instrument is run. All asynchronous instruments (Int64ObservableCounter, Int64ObservableUpDownCounter, Int64ObservableGauge, Float64ObservableCounter, Float64ObservableUpDownCounter, and Float64ObservableGauge) are used to measure metrics outside of the execution of source code. They are said to make "observations" via a callback function called once every measurement collection cycle. Each instrument is also grouped by the value type it measures. Either int64 or float64. The value being measured will dictate which instrument in these categories to use. Outside of these two broad categories, instruments are described by the function they are designed to serve. All Counters (Int64Counter, Float64Counter, Int64ObservableCounter, and Float64ObservableCounter) are designed to measure values that never decrease in value, but instead only incrementally increase in value. UpDownCounters (Int64UpDownCounter, Float64UpDownCounter, Int64ObservableUpDownCounter, and Float64ObservableUpDownCounter) on the other hand, are designed to measure values that can increase and decrease. When more information needs to be conveyed about all the synchronous measurements made during a collection cycle, a Histogram (Int64Histogram and Float64Histogram) should be used. Finally, when just the most recent measurement needs to be conveyed about an asynchronous measurement, a Gauge (Int64ObservableGauge and Float64ObservableGauge) should be used. See the OpenTelemetry documentation for more information about instruments and their intended use. OpenTelemetry defines an instrument name syntax that restricts what instrument names are allowed. Instrument names should ... To ensure compatibility with observability platforms, all instruments created need to conform to this syntax. Not all implementations of the API will validate these names, it is the callers responsibility to ensure compliance. Measurements are made by recording values and information about the values with an instrument. How these measurements are recorded depends on the instrument. Measurements for synchronous instruments (Int64Counter, Int64UpDownCounter, Int64Histogram, Float64Counter, Float64UpDownCounter, and Float64Histogram) are recorded using the instrument methods directly. All counter instruments have an Add method that is used to measure an increment value, and all histogram instruments have a Record method to measure a data point. Asynchronous instruments (Int64ObservableCounter, Int64ObservableUpDownCounter, Int64ObservableGauge, Float64ObservableCounter, Float64ObservableUpDownCounter, and Float64ObservableGauge) record measurements within a callback function. The callback is registered with the Meter which ensures the callback is called once per collection cycle. A callback can be registered two ways: during the instrument's creation using an option, or later using the RegisterCallback method of the Meter that created the instrument. If the following criteria are met, an option (WithInt64Callback or WithFloat64Callback) can be used during the asynchronous instrument's creation to register a callback (Int64Callback or Float64Callback, respectively): If the criteria are not met, use the RegisterCallback method of the Meter that created the instrument to register a Callback. This package does not conform to the standard Go versioning policy, all of its interfaces may have methods added to them without a package major version bump. This non-standard API evolution could surprise an uninformed implementation author. They could unknowingly build their implementation in a way that would result in a runtime panic for their users that update to the new API. The API is designed to help inform an instrumentation author about this non-standard API evolution. It requires them to choose a default behavior for unimplemented interface methods. There are three behavior choices they can make: All interfaces in this API embed a corresponding interface from go.opentelemetry.io/otel/metric/embedded. If an author wants the default behavior of their implementations to be a compilation failure, signaling to their users they need to update to the latest version of that implementation, they need to embed the corresponding interface from go.opentelemetry.io/otel/metric/embedded in their implementation. For example, If an author wants the default behavior of their implementations to a panic, they need to embed the API interface directly. This is not a recommended behavior as it could lead to publishing packages that contain runtime panics when users update other package that use newer versions of go.opentelemetry.io/otel/metric. Finally, an author can embed another implementation in theirs. The embedded implementation will be used for methods not defined by the author. For example, an author who wants to default to silently dropping the call can use go.opentelemetry.io/otel/metric/noop: It is strongly recommended that authors only embed go.opentelemetry.io/otel/metric/noop if they choose this default behavior. That implementation is the only one OpenTelemetry authors can guarantee will fully implement all the API interfaces when a user updates their API.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/metric#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.32.0 (published about 1 month ago)
• Last Synced: 2024-11-15T14:34:39.093Z (about 1 month ago)
• Versions: 49
• Dependent Packages: 8,263
• Dependent Repositories: 21,100
• Docker Downloads: 37,601,304,709
• Rankings:
  • Docker downloads count: 0.011%
  • Dependent packages count: 0.035%
  • Dependent repos count: 0.045%
  • Average: 0.405%
  • Forks count: 0.897%
  • Stargazers count: 1.035%

go: go.opentelemetry.io/otel/sdk/metric

Package metric provides an implementation of the OpenTelemetry metrics SDK. See https://opentelemetry.io/docs/concepts/signals/metrics/ for information about the concept of OpenTelemetry metrics and https://opentelemetry.io/docs/concepts/components/ for more information about OpenTelemetry SDKs. The entry point for the metric package is the MeterProvider. It is the object that all API calls use to create Meters, instruments, and ultimately make metric measurements. Also, it is an object that should be used to control the life-cycle (start, flush, and shutdown) of the SDK. A MeterProvider needs to be configured to export the measured data, this is done by configuring it with a Reader implementation (using the WithReader MeterProviderOption). Readers take two forms: ones that push to an endpoint (NewPeriodicReader), and ones that an endpoint pulls from. See go.opentelemetry.io/otel/exporters for exporters that can be used as or with these Readers. Each Reader, when registered with the MeterProvider, can be augmented with a View. Views allow users that run OpenTelemetry instrumented code to modify the generated data of that instrumentation. The data generated by a MeterProvider needs to include information about its origin. A MeterProvider needs to be configured with a Resource, using the WithResource MeterProviderOption, to include this information. This Resource should be used to describe the unique runtime environment instrumented code is being run on. That way when multiple instances of the code are collected at a single endpoint their origin is decipherable. To avoid leaking memory, the SDK returns the same instrument for calls to create new instruments with the same Name, Unit, and Description. Importantly, callbacks provided using metric.WithFloat64Callback or metric.WithInt64Callback will only apply for the first instrument created with a given Name, Unit, and Description. Instead, use Meter.RegisterCallback and Registration.Unregister to add and remove callbacks without leaking memory. See go.opentelemetry.io/otel/metric for more information about the metric API. See go.opentelemetry.io/otel/sdk/metric/internal/x for information about the experimental features. To enable metrics in your application using the SDK, you'll need to have an initialized MeterProvider that will let you create a go.opentelemetry.io/otel/metric.Meter. Here's how you might initialize a metrics provider.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/sdk/metric#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.31.0 (published 2 months ago)
• Last Synced: 2024-11-11T23:32:44.803Z (about 1 month ago)
• Versions: 48
• Dependent Packages: 3,173
• Dependent Repositories: 15,074
• Docker Downloads: 9,928,066,202
• Rankings:
  • Docker downloads count: 0.056%
  • Dependent repos count: 0.061%
  • Dependent packages count: 0.071%
  • Average: 0.423%
  • Forks count: 0.893%
  • Stargazers count: 1.033%

go: go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc

Package otlptracegrpc provides an OTLP span exporter using gRPC. By default the telemetry is sent to https://localhost:4317. Exporter should be created using New. The environment variables described below can be used for configuration. OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_TRACES_ENDPOINT (default: "https://localhost:4317") - target to which the exporter sends telemetry. The target syntax is defined in https://github.com/grpc/grpc/blob/master/doc/naming.md. The value must contain a scheme ("http" or "https") and host. The value may additionally contain a port, and a path. The value should not contain a query string or fragment. OTEL_EXPORTER_OTLP_TRACES_ENDPOINT takes precedence over OTEL_EXPORTER_OTLP_ENDPOINT. The configuration can be overridden by WithEndpoint, WithEndpointURL, WithInsecure, and WithGRPCConn options. OTEL_EXPORTER_OTLP_INSECURE, OTEL_EXPORTER_OTLP_TRACES_INSECURE (default: "false") - setting "true" disables client transport security for the exporter's gRPC connection. You can use this only when an endpoint is provided without the http or https scheme. OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_TRACES_ENDPOINT setting overrides the scheme defined via OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_TRACES_ENDPOINT. OTEL_EXPORTER_OTLP_TRACES_INSECURE takes precedence over OTEL_EXPORTER_OTLP_INSECURE. The configuration can be overridden by WithInsecure, WithGRPCConn options. OTEL_EXPORTER_OTLP_HEADERS, OTEL_EXPORTER_OTLP_TRACES_HEADERS (default: none) - key-value pairs used as gRPC metadata associated with gRPC requests. The value is expected to be represented in a format matching the W3C Baggage HTTP Header Content Format, except that additional semi-colon delimited metadata is not supported. Example value: "key1=value1,key2=value2". OTEL_EXPORTER_OTLP_TRACES_HEADERS takes precedence over OTEL_EXPORTER_OTLP_HEADERS. The configuration can be overridden by WithHeaders option. OTEL_EXPORTER_OTLP_TIMEOUT, OTEL_EXPORTER_OTLP_TRACES_TIMEOUT (default: "10000") - maximum time in milliseconds the OTLP exporter waits for each batch export. OTEL_EXPORTER_OTLP_TRACES_TIMEOUT takes precedence over OTEL_EXPORTER_OTLP_TIMEOUT. The configuration can be overridden by WithTimeout option. OTEL_EXPORTER_OTLP_COMPRESSION, OTEL_EXPORTER_OTLP_TRACES_COMPRESSION (default: none) - the gRPC compressor the exporter uses. Supported value: "gzip". OTEL_EXPORTER_OTLP_TRACES_COMPRESSION takes precedence over OTEL_EXPORTER_OTLP_COMPRESSION. The configuration can be overridden by WithCompressor, WithGRPCConn options. OTEL_EXPORTER_OTLP_CERTIFICATE, OTEL_EXPORTER_OTLP_TRACES_CERTIFICATE (default: none) - the filepath to the trusted certificate to use when verifying a server's TLS credentials. OTEL_EXPORTER_OTLP_TRACES_CERTIFICATE takes precedence over OTEL_EXPORTER_OTLP_CERTIFICATE. The configuration can be overridden by WithTLSCredentials, WithGRPCConn options. OTEL_EXPORTER_OTLP_CLIENT_CERTIFICATE, OTEL_EXPORTER_OTLP_TRACES_CLIENT_CERTIFICATE (default: none) - the filepath to the client certificate/chain trust for client's private key to use in mTLS communication in PEM format. OTEL_EXPORTER_OTLP_TRACES_CLIENT_CERTIFICATE takes precedence over OTEL_EXPORTER_OTLP_CLIENT_CERTIFICATE. The configuration can be overridden by WithTLSCredentials, WithGRPCConn options. OTEL_EXPORTER_OTLP_CLIENT_KEY, OTEL_EXPORTER_OTLP_TRACES_CLIENT_KEY (default: none) - the filepath to the client's private key to use in mTLS communication in PEM format. OTEL_EXPORTER_OTLP_TRACES_CLIENT_KEY takes precedence over OTEL_EXPORTER_OTLP_CLIENT_KEY. The configuration can be overridden by WithTLSCredentials, WithGRPCConn option.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.32.0 (published about 1 month ago)
• Last Synced: 2024-11-16T02:03:01.237Z (about 1 month ago)
• Versions: 50
• Dependent Packages: 3,626
• Dependent Repositories: 7,567
• Docker Downloads: 23,473,722,529
• Rankings:
  • Docker downloads count: 0.021%
  • Dependent packages count: 0.072%
  • Dependent repos count: 0.091%
  • Average: 0.423%
  • Forks count: 0.897%
  • Stargazers count: 1.035%

go: go.opentelemetry.io/otel/exporters/otlp/internal/retry

Package retry provides request retry functionality that can perform configurable exponential backoff for transient errors and honor any explicit throttle responses received. Deprecated: package retry exists for historical compatibility, it should not be used.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp/internal/retry#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.17.0 (published over 1 year ago)
• Last Synced: 2024-11-15T17:02:28.358Z (about 1 month ago)
• Versions: 25
• Dependent Packages: 3,479
• Dependent Repositories: 5,636
• Docker Downloads: 20,195,003,285
• Rankings:
  • Docker downloads count: 0.021%
  • Dependent packages count: 0.074%
  • Dependent repos count: 0.11%
  • Average: 0.424%
  • Forks count: 0.889%
  • Stargazers count: 1.028%

go: go.opentelemetry.io/otel/sdk/export/metric

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/sdk/export/metric#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.28.0 (published over 2 years ago)
• Last Synced: 2024-11-10T22:01:46.868Z (about 1 month ago)
• Versions: 12
• Dependent Packages: 1,724
• Dependent Repositories: 14,235
• Docker Downloads: 3,879,162,485
• Rankings:
  • Dependent repos count: 0.063%
  • Docker downloads count: 0.071%
  • Dependent packages count: 0.087%
  • Average: 0.431%
  • Forks count: 0.897%
  • Stargazers count: 1.035%

go: go.opentelemetry.io/otel/exporters/otlp

Deprecated: This package was moved to exporters/otlp/otlptrace and exporters/otlp/otlpmetric.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.20.1 (published almost 2 years ago)
• Last Synced: 2024-11-10T18:04:19.577Z (about 1 month ago)
• Versions: 22
• Dependent Packages: 1,317
• Dependent Repositories: 13,703
• Docker Downloads: 3,731,673,319
• Rankings:
  • Dependent repos count: 0.065%
  • Docker downloads count: 0.072%
  • Dependent packages count: 0.101%
  • Average: 0.434%
  • Forks count: 0.897%
  • Stargazers count: 1.035%

go: go.opentelemetry.io/otel/exporters/jaeger

Package jaeger contains an OpenTelemetry tracing exporter for Jaeger. Deprecated: This module is no longer supported. OpenTelemetry dropped support for Jaeger exporter in July 2023. Jaeger officially accepts and recommends using OTLP. Use go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp or go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc instead.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/jaeger#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.17.0 (published over 1 year ago)
• Last Synced: 2024-11-27T14:31:19.372Z (24 days ago)
• Versions: 32
• Dependent Packages: 2,496
• Dependent Repositories: 3,055
• Docker Downloads: 5,436,250,766
• Rankings:
  • Docker downloads count: 0.047%
  • Dependent packages count: 0.073%
  • Dependent repos count: 0.143%
  • Average: 0.439%
  • Forks count: 0.902%
  • Stargazers count: 1.03%

go: go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp

Package otlptracehttp provides an OTLP span exporter using HTTP with protobuf payloads. By default the telemetry is sent to https://localhost:4318/v1/traces. Exporter should be created using New. The environment variables described below can be used for configuration. OTEL_EXPORTER_OTLP_ENDPOINT (default: "https://localhost:4318") - target base URL ("/v1/traces" is appended) to which the exporter sends telemetry. The value must contain a scheme ("http" or "https") and host. The value may additionally contain a port and a path. The value should not contain a query string or fragment. The configuration can be overridden by OTEL_EXPORTER_OTLP_TRACES_ENDPOINT environment variable and by WithEndpoint, WithEndpointURL, WithInsecure options. OTEL_EXPORTER_OTLP_TRACES_ENDPOINT (default: "https://localhost:4318/v1/traces") - target URL to which the exporter sends telemetry. The value must contain a scheme ("http" or "https") and host. The value may additionally contain a port and a path. The value should not contain a query string or fragment. The configuration can be overridden by WithEndpoint, WithEndpointURL, WithInsecure, and WithURLPath options. OTEL_EXPORTER_OTLP_HEADERS, OTEL_EXPORTER_OTLP_TRACES_HEADERS (default: none) - key-value pairs used as headers associated with HTTP requests. The value is expected to be represented in a format matching the W3C Baggage HTTP Header Content Format, except that additional semi-colon delimited metadata is not supported. Example value: "key1=value1,key2=value2". OTEL_EXPORTER_OTLP_TRACES_HEADERS takes precedence over OTEL_EXPORTER_OTLP_HEADERS. The configuration can be overridden by WithHeaders option. OTEL_EXPORTER_OTLP_TIMEOUT, OTEL_EXPORTER_OTLP_TRACES_TIMEOUT (default: "10000") - maximum time in milliseconds the OTLP exporter waits for each batch export. OTEL_EXPORTER_OTLP_TRACES_TIMEOUT takes precedence over OTEL_EXPORTER_OTLP_TIMEOUT. The configuration can be overridden by WithTimeout option. OTEL_EXPORTER_OTLP_COMPRESSION, OTEL_EXPORTER_OTLP_TRACES_COMPRESSION (default: none) - the compression strategy the exporter uses to compress the HTTP body. Supported value: "gzip". OTEL_EXPORTER_OTLP_TRACES_COMPRESSION takes precedence over OTEL_EXPORTER_OTLP_COMPRESSION. The configuration can be overridden by WithCompression option. OTEL_EXPORTER_OTLP_CERTIFICATE, OTEL_EXPORTER_OTLP_TRACES_CERTIFICATE (default: none) - the filepath to the trusted certificate to use when verifying a server's TLS credentials. OTEL_EXPORTER_OTLP_TRACES_CERTIFICATE takes precedence over OTEL_EXPORTER_OTLP_CERTIFICATE. The configuration can be overridden by WithTLSClientConfig option. OTEL_EXPORTER_OTLP_CLIENT_CERTIFICATE, OTEL_EXPORTER_OTLP_TRACES_CLIENT_CERTIFICATE (default: none) - the filepath to the client certificate/chain trust for client's private key to use in mTLS communication in PEM format. OTEL_EXPORTER_OTLP_TRACES_CLIENT_CERTIFICATE takes precedence over OTEL_EXPORTER_OTLP_CLIENT_CERTIFICATE. The configuration can be overridden by WithTLSClientConfig option. OTEL_EXPORTER_OTLP_CLIENT_KEY, OTEL_EXPORTER_OTLP_TRACES_CLIENT_KEY (default: none) - the filepath to the client's private key to use in mTLS communication in PEM format. OTEL_EXPORTER_OTLP_TRACES_CLIENT_KEY takes precedence over OTEL_EXPORTER_OTLP_CLIENT_KEY. The configuration can be overridden by WithTLSClientConfig option.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.32.0 (published about 1 month ago)
• Last Synced: 2024-11-16T02:02:31.144Z (about 1 month ago)
• Versions: 50
• Dependent Packages: 1,397
• Dependent Repositories: 3,979
• Docker Downloads: 14,135,307,558
• Rankings:
  • Docker downloads count: 0.033%
  • Dependent repos count: 0.131%
  • Dependent packages count: 0.141%
  • Average: 0.449%
  • Forks count: 0.9%
  • Stargazers count: 1.039%

go: go.opentelemetry.io/otel/internal/metric

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/internal/metric#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.27.0 (published almost 3 years ago)
• Last Synced: 2024-11-13T04:00:46.924Z (about 1 month ago)
• Versions: 7
• Dependent Packages: 1,169
• Dependent Repositories: 2,017
• Docker Downloads: 9,941,495,562
• Rankings:
  • Docker downloads count: 0.033%
  • Dependent packages count: 0.112%
  • Dependent repos count: 0.183%
  • Average: 0.453%
  • Forks count: 0.899%
  • Stargazers count: 1.038%

go: go.opentelemetry.io/otel/exporters/stdout/stdouttrace

Package stdouttrace contains an OpenTelemetry exporter for tracing telemetry to be written to an output destination as JSON.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/stdout/stdouttrace#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.32.0 (published about 1 month ago)
• Last Synced: 2024-11-23T15:01:51.004Z (28 days ago)
• Versions: 50
• Dependent Packages: 1,288
• Dependent Repositories: 764
• Docker Downloads: 3,674,762,968
• Rankings:
  • Dependent packages count: 0.14%
  • Docker downloads count: 0.175%
  • Dependent repos count: 0.272%
  • Average: 0.505%
  • Forks count: 0.899%
  • Stargazers count: 1.038%

go: go.opentelemetry.io/otel/exporters/prometheus

Package prometheus provides a Prometheus Exporter that converts OTLP metrics into the Prometheus exposition format and implements prometheus.Collector to provide a handler for these metrics.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/prometheus#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.46.0 (published 10 months ago)
• Last Synced: 2024-11-11T21:00:28.288Z (about 1 month ago)
• Versions: 43
• Dependent Packages: 879
• Dependent Repositories: 1,043
• Docker Downloads: 3,939,059,061
• Rankings:
  • Dependent packages count: 0.139%
  • Docker downloads count: 0.226%
  • Dependent repos count: 0.235%
  • Average: 0.506%
  • Forks count: 0.902%
  • Stargazers count: 1.03%

go: go.opentelemetry.io/otel/exporters/zipkin

Package zipkin contains an OpenTelemetry tracing exporter for Zipkin.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/zipkin#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T04:02:10.622Z (about 1 month ago)
• Versions: 50
• Dependent Packages: 995
• Dependent Repositories: 898
• Docker Downloads: 136,039,789
• Rankings:
  • Dependent packages count: 0.143%
  • Docker downloads count: 0.239%
  • Dependent repos count: 0.255%
  • Average: 0.512%
  • Forks count: 0.89%
  • Stargazers count: 1.03%

go: go.opentelemetry.io/otel/oteltest

Deprecated: This package was removed, some functionality is found in sdk/trace/tracetest.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/oteltest#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.20.1 (published almost 2 years ago)
• Last Synced: 2024-11-13T17:32:02.433Z (about 1 month ago)
• Versions: 8
• Dependent Packages: 317
• Dependent Repositories: 18,160
• Docker Downloads: 16,311,680
• Rankings:
  • Dependent repos count: 0.052%
  • Dependent packages count: 0.23%
  • Docker downloads count: 0.384%
  • Average: 0.519%
  • Forks count: 0.895%
  • Stargazers count: 1.035%

go: go.opentelemetry.io/otel/exporters/otlp/otlpmetric

Package otlpmetric provides an OpenTelemetry metric Exporter that can be used with PeriodicReader. It transforms metricdata into OTLP and transmits the transformed data to OTLP receivers. The Exporter is configurable to use different Clients, each using a distinct transport protocol to communicate to an OTLP receiving endpoint. Deprecated: Use go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc or go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp instead.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp/otlpmetric#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.43.0 (published about 1 year ago)
• Last Synced: 2024-11-10T07:02:14.904Z (about 1 month ago)
• Versions: 31
• Dependent Packages: 873
• Dependent Repositories: 764
• Docker Downloads: 1,570,719,655
• Rankings:
  • Dependent packages count: 0.161%
  • Dependent repos count: 0.272%
  • Docker downloads count: 0.426%
  • Average: 0.557%
  • Forks count: 0.893%
  • Stargazers count: 1.033%

go: go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc

Package otlpmetricgrpc provides an OTLP metrics exporter using gRPC. By default the telemetry is sent to https://localhost:4317. Exporter should be created using New and used with a metric.PeriodicReader. The environment variables described below can be used for configuration. OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_METRICS_ENDPOINT (default: "https://localhost:4317") - target to which the exporter sends telemetry. The target syntax is defined in https://github.com/grpc/grpc/blob/master/doc/naming.md. The value must contain a scheme ("http" or "https") and host. The value may additionally contain a port, and a path. The value should not contain a query string or fragment. OTEL_EXPORTER_OTLP_METRICS_ENDPOINT takes precedence over OTEL_EXPORTER_OTLP_ENDPOINT. The configuration can be overridden by WithEndpoint, WithEndpointURL, WithInsecure, and WithGRPCConn options. OTEL_EXPORTER_OTLP_INSECURE, OTEL_EXPORTER_OTLP_METRICS_INSECURE (default: "false") - setting "true" disables client transport security for the exporter's gRPC connection. You can use this only when an endpoint is provided without the http or https scheme. OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_METRICS_ENDPOINT setting overrides the scheme defined via OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_METRICS_ENDPOINT. OTEL_EXPORTER_OTLP_METRICS_INSECURE takes precedence over OTEL_EXPORTER_OTLP_INSECURE. The configuration can be overridden by WithInsecure, WithGRPCConn options. OTEL_EXPORTER_OTLP_HEADERS, OTEL_EXPORTER_OTLP_METRICS_HEADERS (default: none) - key-value pairs used as gRPC metadata associated with gRPC requests. The value is expected to be represented in a format matching the W3C Baggage HTTP Header Content Format, except that additional semi-colon delimited metadata is not supported. Example value: "key1=value1,key2=value2". OTEL_EXPORTER_OTLP_METRICS_HEADERS takes precedence over OTEL_EXPORTER_OTLP_HEADERS. The configuration can be overridden by WithHeaders option. OTEL_EXPORTER_OTLP_TIMEOUT, OTEL_EXPORTER_OTLP_METRICS_TIMEOUT (default: "10000") - maximum time in milliseconds the OTLP exporter waits for each batch export. OTEL_EXPORTER_OTLP_METRICS_TIMEOUT takes precedence over OTEL_EXPORTER_OTLP_TIMEOUT. The configuration can be overridden by WithTimeout option. OTEL_EXPORTER_OTLP_COMPRESSION, OTEL_EXPORTER_OTLP_METRICS_COMPRESSION (default: none) - the gRPC compressor the exporter uses. Supported value: "gzip". OTEL_EXPORTER_OTLP_METRICS_COMPRESSION takes precedence over OTEL_EXPORTER_OTLP_COMPRESSION. The configuration can be overridden by WithCompressor, WithGRPCConn options. OTEL_EXPORTER_OTLP_CERTIFICATE, OTEL_EXPORTER_OTLP_METRICS_CERTIFICATE (default: none) - the filepath to the trusted certificate to use when verifying a server's TLS credentials. OTEL_EXPORTER_OTLP_METRICS_CERTIFICATE takes precedence over OTEL_EXPORTER_OTLP_CERTIFICATE. The configuration can be overridden by WithTLSCredentials, WithGRPCConn options. OTEL_EXPORTER_OTLP_CLIENT_CERTIFICATE, OTEL_EXPORTER_OTLP_METRICS_CLIENT_CERTIFICATE (default: none) - the filepath to the client certificate/chain trust for client's private key to use in mTLS communication in PEM format. OTEL_EXPORTER_OTLP_METRICS_CLIENT_CERTIFICATE takes precedence over OTEL_EXPORTER_OTLP_CLIENT_CERTIFICATE. The configuration can be overridden by WithTLSCredentials, WithGRPCConn options. OTEL_EXPORTER_OTLP_CLIENT_KEY, OTEL_EXPORTER_OTLP_METRICS_CLIENT_KEY (default: none) - the filepath to the client's private key to use in mTLS communication in PEM format. OTEL_EXPORTER_OTLP_METRICS_CLIENT_KEY takes precedence over OTEL_EXPORTER_OTLP_CLIENT_KEY. The configuration can be overridden by WithTLSCredentials, WithGRPCConn option. OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE (default: "cumulative") - aggregation temporality to use on the basis of instrument kind. Supported values: The configuration can be overridden by WithTemporalitySelector option. OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION (default: "explicit_bucket_histogram") - default aggregation to use for histogram instruments. Supported values: The configuration can be overridden by WithAggregationSelector option.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.32.0 (published about 1 month ago)
• Last Synced: 2024-11-19T09:02:26.469Z (about 1 month ago)
• Versions: 45
• Dependent Packages: 796
• Dependent Repositories: 702
• Docker Downloads: 3,212,892,552
• Rankings:
  • Dependent packages count: 0.173%
  • Dependent repos count: 0.281%
  • Docker downloads count: 0.426%
  • Average: 0.561%
  • Forks count: 0.893%
  • Stargazers count: 1.033%

go: go.opentelemetry.io/otel/exporters/metric/prometheus

Package prometheus provices an OpenTelemetry metrics exporter for Prometheus. Deprecated: Use Prometheus exporter in package go.opentelemetry.io/otel/exporters/prometheus. This package is frozen and no new functionality will be added.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/metric/prometheus#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.21.0 (published over 3 years ago)
• Last Synced: 2024-11-11T19:00:43.632Z (about 1 month ago)
• Versions: 23
• Dependent Packages: 138
• Dependent Repositories: 203
• Docker Downloads: 2,150,207,869
• Rankings:
  • Docker downloads count: 0.146%
  • Dependent packages count: 0.387%
  • Dependent repos count: 0.447%
  • Average: 0.579%
  • Forks count: 0.893%
  • Stargazers count: 1.021%

go: go.opentelemetry.io/otel/exporters/trace/jaeger

Deprecated: This package was moved to exporters/jaeger.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/trace/jaeger#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.20.1 (published almost 2 years ago)
• Last Synced: 2024-11-11T20:01:34.592Z (about 1 month ago)
• Versions: 24
• Dependent Packages: 206
• Dependent Repositories: 292
• Docker Downloads: 3,498,322
• Rankings:
  • Dependent packages count: 0.281%
  • Dependent repos count: 0.39%
  • Docker downloads count: 0.483%
  • Average: 0.638%
  • Forks count: 0.935%
  • Stargazers count: 1.099%

go: go.opentelemetry.io/otel/exporters/stdout/stdoutmetric

Package stdoutmetric provides an exporter for OpenTelemetry metric telemetry. The exporter is intended to be used for testing and debugging, it is not meant for production use. Additionally, it does not provide an interchange format for OpenTelemetry that is supported with any stability or compatibility guarantees. If these are needed features, please use the OTLP exporter instead.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/stdout/stdoutmetric#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.32.0 (published about 1 month ago)
• Last Synced: 2024-11-20T14:32:39.226Z (about 1 month ago)
• Versions: 45
• Dependent Packages: 228
• Dependent Repositories: 115
• Docker Downloads: 3,540,935,596
• Rankings:
  • Docker downloads count: 0.194%
  • Dependent packages count: 0.503%
  • Dependent repos count: 0.567%
  • Average: 0.641%
  • Forks count: 0.9%
  • Stargazers count: 1.039%

go: go.opentelemetry.io/otel/bridge/opentracing

Package opentracing implements a bridge that forwards OpenTracing API calls to the OpenTelemetry SDK. To use the bridge, first create an OpenTelemetry tracer of choice. Then use the NewTracerPair() function to create two tracers - one implementing OpenTracing API (BridgeTracer) and one that implements the OpenTelemetry API (WrapperTracer) and mostly forwards the calls to the OpenTelemetry tracer of choice, but does some extra steps to make the interaction between both APIs working. If the OpenTelemetry tracer of choice already knows how to cooperate with OpenTracing API through the OpenTracing bridge (explained in detail below), then it is fine to skip the WrapperTracer by calling the NewBridgeTracer() function to get the bridge tracer and then passing the chosen OpenTelemetry tracer to the SetOpenTelemetryTracer() function of the bridge tracer. To use an OpenTelemetry span as the parent of an OpenTracing span, create a context using the ContextWithBridgeSpan() function of the bridge tracer, and then use the StartSpanFromContext function of the OpenTracing API. Bridge tracer also allows the user to install a warning handler through the SetWarningHandler() function. The warning handler will be called when there is some misbehavior of the OpenTelemetry tracer with regard to the cooperation with the OpenTracing API. For an OpenTelemetry tracer to cooperate with OpenTracing API through the BridgeTracer, the OpenTelemetry tracer needs to (reasoning is below the list): 1. Return the same context it received in the Start() function if migration.SkipContextSetup() returns true. 2. Implement the migration.DeferredContextSetupTracerExtension interface. The implementation should setup the context it would normally do in the Start() function if the migration.SkipContextSetup() function returned false. Calling ContextWithBridgeSpan() is not necessary. 3. Have an access to the BridgeTracer instance. 4. If the migration.SkipContextSetup() function returned false, the tracer should use the ContextWithBridgeSpan() function to install the created span as an active OpenTracing span. There are some differences between OpenTracing and OpenTelemetry APIs, especially with regard to Go context handling. When a span is created with an OpenTracing API (through the StartSpan() function) the Go context is not available. BridgeTracer has access to the OpenTelemetry tracer of choice, so in the StartSpan() function BridgeTracer translates the parameters to the OpenTelemetry version and uses the OpenTelemetry tracer's Start() function to actually create a span. The OpenTelemetry Start() function takes the Go context as a parameter, so BridgeTracer at this point passes a temporary context to Start(). All the changes to the temporary context will be lost at the end of the StartSpan() function, so the OpenTelemetry tracer of choice should not do anything with the context. If the returned context is different, BridgeTracer will warn about it. The OpenTelemetry tracer of choice can learn about this situation by using the migration.SkipContextSetup() function. The tracer will receive an opportunity to set up the context at a later stage. Usually after StartSpan() is finished, users of the OpenTracing API are calling (either directly or through the opentracing.StartSpanFromContext() helper function) the opentracing.ContextWithSpan() function to insert the created OpenTracing span into the context. At that time, the OpenTelemetry tracer of choice has a chance of setting up the context through a hook invoked inside the opentracing.ContextWithSpan() function. For that to happen, the tracer should implement the migration.DeferredContextSetupTracerExtension interface. This so far explains the need for points 1. and 2. When the span is created with the OpenTelemetry API (with the Start() function) then migration.SkipContextSetup() will return false. This means that the tracer can do the usual setup of the context, but it also should set up the active OpenTracing span in the context. This is because OpenTracing API is not used at all in the creation of the span, but the OpenTracing API may be used during the time when the created OpenTelemetry span is current. For this case to work, we need to also set up active OpenTracing span in the context. This can be done with the ContextWithBridgeSpan() function. This means that the OpenTelemetry tracer of choice needs to have an access to the BridgeTracer instance. This should explain the need for points 3. and 4. Another difference related to the Go context handling is in logging - OpenTracing API does not take a context parameter in the LogFields() function, so when the call to the function gets translated to OpenTelemetry AddEvent() function, an empty context is passed.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/bridge/opentracing#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.32.0 (published about 1 month ago)
• Last Synced: 2024-11-15T21:00:56.254Z (about 1 month ago)
• Versions: 60
• Dependent Packages: 97
• Dependent Repositories: 141
• Docker Downloads: 96,495,470
• Rankings:
  • Docker downloads count: 0.278%
  • Dependent packages count: 0.488%
  • Dependent repos count: 0.52%
  • Average: 0.644%
  • Forks count: 0.897%
  • Stargazers count: 1.035%

go: go.opentelemetry.io/otel/exporters/stdout

Deprecated: This package was split into exporters/stdout/stdouttrace and exporters/stdout/stdoutmetric.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/stdout#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.20.1 (published almost 2 years ago)
• Last Synced: 2024-11-11T13:31:40.529Z (about 1 month ago)
• Versions: 12
• Dependent Packages: 207
• Dependent Repositories: 201
• Docker Downloads: 617,126
• Rankings:
  • Dependent packages count: 0.303%
  • Dependent repos count: 0.448%
  • Docker downloads count: 0.592%
  • Average: 0.655%
  • Forks count: 0.902%
  • Stargazers count: 1.03%

go: go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp

Package otlpmetrichttp provides an OTLP metrics exporter using HTTP with protobuf payloads. By default the telemetry is sent to https://localhost:4318/v1/metrics. Exporter should be created using New and used with a metric.PeriodicReader. The environment variables described below can be used for configuration. OTEL_EXPORTER_OTLP_ENDPOINT (default: "https://localhost:4318") - target base URL ("/v1/metrics" is appended) to which the exporter sends telemetry. The value must contain a scheme ("http" or "https") and host. The value may additionally contain a port and a path. The value should not contain a query string or fragment. The configuration can be overridden by OTEL_EXPORTER_OTLP_METRICS_ENDPOINT environment variable and by WithEndpoint, WithEndpointURL, and WithInsecure options. OTEL_EXPORTER_OTLP_METRICS_ENDPOINT (default: "https://localhost:4318/v1/metrics") - target URL to which the exporter sends telemetry. The value must contain a scheme ("http" or "https") and host. The value may additionally contain a port and a path. The value should not contain a query string or fragment. The configuration can be overridden by WithEndpoint, WithEndpointURL, WithInsecure, and WithURLPath options. OTEL_EXPORTER_OTLP_HEADERS, OTEL_EXPORTER_OTLP_METRICS_HEADERS (default: none) - key-value pairs used as headers associated with HTTP requests. The value is expected to be represented in a format matching the W3C Baggage HTTP Header Content Format, except that additional semi-colon delimited metadata is not supported. Example value: "key1=value1,key2=value2". OTEL_EXPORTER_OTLP_METRICS_HEADERS takes precedence over OTEL_EXPORTER_OTLP_HEADERS. The configuration can be overridden by WithHeaders option. OTEL_EXPORTER_OTLP_TIMEOUT, OTEL_EXPORTER_OTLP_METRICS_TIMEOUT (default: "10000") - maximum time in milliseconds the OTLP exporter waits for each batch export. OTEL_EXPORTER_OTLP_METRICS_TIMEOUT takes precedence over OTEL_EXPORTER_OTLP_TIMEOUT. The configuration can be overridden by WithTimeout option. OTEL_EXPORTER_OTLP_COMPRESSION, OTEL_EXPORTER_OTLP_METRICS_COMPRESSION (default: none) - compression strategy the exporter uses to compress the HTTP body. Supported values: "gzip". OTEL_EXPORTER_OTLP_METRICS_COMPRESSION takes precedence over OTEL_EXPORTER_OTLP_COMPRESSION. The configuration can be overridden by WithCompression option. OTEL_EXPORTER_OTLP_CERTIFICATE, OTEL_EXPORTER_OTLP_METRICS_CERTIFICATE (default: none) - filepath to the trusted certificate to use when verifying a server's TLS credentials. OTEL_EXPORTER_OTLP_METRICS_CERTIFICATE takes precedence over OTEL_EXPORTER_OTLP_CERTIFICATE. The configuration can be overridden by WithTLSClientConfig option. OTEL_EXPORTER_OTLP_CLIENT_CERTIFICATE, OTEL_EXPORTER_OTLP_METRICS_CLIENT_CERTIFICATE (default: none) - filepath to the client certificate/chain trust for client's private key to use in mTLS communication in PEM format. OTEL_EXPORTER_OTLP_METRICS_CLIENT_CERTIFICATE takes precedence over OTEL_EXPORTER_OTLP_CLIENT_CERTIFICATE. The configuration can be overridden by WithTLSClientConfig option. OTEL_EXPORTER_OTLP_CLIENT_KEY, OTEL_EXPORTER_OTLP_METRICS_CLIENT_KEY (default: none) - filepath to the client's private key to use in mTLS communication in PEM format. OTEL_EXPORTER_OTLP_METRICS_CLIENT_KEY takes precedence over OTEL_EXPORTER_OTLP_CLIENT_KEY. The configuration can be overridden by WithTLSClientConfig option. OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE (default: "cumulative") - aggregation temporality to use on the basis of instrument kind. Supported values: The configuration can be overridden by WithTemporalitySelector option. OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION (default: "explicit_bucket_histogram") - default aggregation to use for histogram instruments. Supported values: The configuration can be overridden by WithAggregationSelector option.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.32.0 (published about 1 month ago)
• Last Synced: 2024-11-18T19:30:25.972Z (about 1 month ago)
• Versions: 44
• Dependent Packages: 240
• Dependent Repositories: 161
• Docker Downloads: 3,209,451,817
• Rankings:
  • Docker downloads count: 0.427%
  • Dependent packages count: 0.45%
  • Dependent repos count: 0.492%
  • Average: 0.66%
  • Forks count: 0.896%
  • Stargazers count: 1.035%

go: go.opentelemetry.io/otel/bridge/opencensus

Package opencensus provides a migration bridge from OpenCensus to OpenTelemetry for metrics and traces. The bridge incorporates metrics and traces from OpenCensus into the OpenTelemetry SDK, combining them with metrics and traces from OpenTelemetry instrumentation. For most applications, it would be difficult to migrate an application from OpenCensus to OpenTelemetry all-at-once. Libraries used by the application may still be using OpenCensus, and the application itself may have many lines of instrumentation. Bridges help in this situation by allowing your application to have "mixed" instrumentation, while incorporating all instrumentation into a single export path. To migrate with bridges, a user would: With this approach, you can migrate your telemetry, including in dependent libraries over time without disruption. Installing a metric or tracing bridge will cause OpenCensus telemetry to be exported by OpenTelemetry exporters. Since OpenCensus telemetry uses globals, installing a bridge will result in telemetry collection from _all_ libraries that use OpenCensus, including some you may not expect, such as the telemetry exporter itself. There are known limitations to the trace bridge: There are known limitations to the metric bridge:

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/bridge/opencensus#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.24.0 (published 10 months ago)
• Last Synced: 2024-11-11T18:31:26.934Z (about 1 month ago)
• Versions: 51
• Dependent Packages: 265
• Dependent Repositories: 197
• Docker Downloads: 1,571,253,747
• Rankings:
  • Docker downloads count: 0.397%
  • Dependent repos count: 0.453%
  • Dependent packages count: 0.521%
  • Average: 0.661%
  • Forks count: 0.896%
  • Stargazers count: 1.035%

go: go.opentelemetry.io/otel/exporter/trace/jaeger

Package jaeger contains an OpenTelemetry tracing exporter for Jaeger.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporter/trace/jaeger#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.0.0 (published about 5 years ago)
• Last Synced: 2024-12-04T04:01:23.387Z (17 days ago)
• Versions: 6
• Dependent Packages: 22
• Dependent Repositories: 17
• Docker Downloads: 786,538,839
• Rankings:
  • Docker downloads count: 0.135%
  • Average: 0.867%
  • Forks count: 0.899%
  • Dependent packages count: 0.946%
  • Stargazers count: 1.036%
  • Dependent repos count: 1.32%

go: go.opentelemetry.io/otel/exporters/trace/zipkin

Deprecated: This package was moved to exporters/zipkin.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/trace/zipkin#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.20.1 (published almost 2 years ago)
• Last Synced: 2024-10-30T03:02:16.273Z (about 2 months ago)
• Versions: 23
• Dependent Packages: 39
• Dependent Repositories: 84
• Docker Downloads: 89
• Rankings:
  • Dependent repos count: 0.643%
  • Dependent packages count: 0.717%
  • Forks count: 0.899%
  • Average: 1.029%
  • Stargazers count: 1.038%
  • Docker downloads count: 1.848%

go: go.opentelemetry.io/otel/exporter/trace/stackdriver

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporter/trace/stackdriver#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.2.1 (published almost 5 years ago)
• Last Synced: 2024-11-11T14:30:46.321Z (about 1 month ago)
• Versions: 5
• Dependent Packages: 4
• Dependent Repositories: 13
• Docker Downloads: 786,538,384
• Rankings:
  • Docker downloads count: 0.135%
  • Forks count: 0.899%
  • Stargazers count: 1.036%
  • Average: 1.223%
  • Dependent repos count: 1.51%
  • Dependent packages count: 2.536%

go: go.opentelemetry.io/otel/exporter/metric/prometheus

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporter/metric/prometheus#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.2.1 (published almost 5 years ago)
• Last Synced: 2024-11-14T07:01:10.141Z (about 1 month ago)
• Versions: 2
• Dependent Packages: 8
• Dependent Repositories: 3
• Docker Downloads: 455
• Rankings:
  • Forks count: 0.893%
  • Stargazers count: 1.033%
  • Docker downloads count: 1.186%
  • Average: 1.557%
  • Dependent packages count: 1.702%
  • Dependent repos count: 2.971%

go: go.opentelemetry.io/contrib/propagation/opencensus

Package otel provides global access to the OpenTelemetry API. The subpackages of the otel package provide an implementation of the OpenTelemetry API. The provided API is used to instrument code and measure data about that code's performance and operation. The measured data, by default, is not processed or transmitted anywhere. An implementation of the OpenTelemetry SDK, like the default SDK implementation (go.opentelemetry.io/otel/sdk), and associated exporters are used to process and transport this data. To read the getting started guide, see https://opentelemetry.io/docs/languages/go/getting-started/. To read more about tracing, see go.opentelemetry.io/otel/trace. To read more about metrics, see go.opentelemetry.io/otel/metric. To read more about logs, see go.opentelemetry.io/otel/log. To read more about propagation, see go.opentelemetry.io/otel/propagation and go.opentelemetry.io/otel/baggage.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/contrib/propagation/opencensus#section-documentation
• Licenses: Apache-2.0
• Latest release: not found: module go.opentelemetry.io/contrib/propagation/opencensus: no matching versions for query "latest" (published about 2 years ago)
• Last Synced: 2024-11-11T01:37:02.167Z (about 1 month ago)
• Versions: 1
• Dependent Packages: 2
• Dependent Repositories: 5
• Rankings:
  • Forks count: 0.934%
  • Stargazers count: 1.099%
  • Average: 2.015%
  • Dependent repos count: 2.32%
  • Dependent packages count: 3.706%

go: go.opentelemetry.io/otel/example/grpc

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/example/grpc#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.10.0 (published over 4 years ago)
• Last Synced: 2024-11-27T07:19:53.815Z (24 days ago)
• Versions: 13
• Dependent Packages: 2
• Dependent Repositories: 2
• Rankings:
  • Forks count: 0.883%
  • Stargazers count: 1.022%
  • Average: 2.297%
  • Dependent repos count: 3.578%
  • Dependent packages count: 3.706%

go: go.opentelemetry.io/otel/exporters/trace/stackdriver

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/trace/stackdriver#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.2.3 (published almost 5 years ago)
• Last Synced: 2024-11-28T07:31:28.832Z (23 days ago)
• Versions: 1
• Dependent Packages: 2
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.634%
  • Stargazers count: 0.682%
  • Dependent packages count: 3.371%
  • Average: 3.508%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go

Package otel provides global access to the OpenTelemetry API. The subpackages of the otel package provide an implementation of the OpenTelemetry API. The provided API is used to instrument code and measure data about that code's performance and operation. The measured data, by default, is not processed or transmitted anywhere. An implementation of the OpenTelemetry SDK, like the default SDK implementation (go.opentelemetry.io/otel/sdk), and associated exporters are used to process and transport this data. To read the getting started guide, see https://opentelemetry.io/docs/languages/go/getting-started/. To read more about tracing, see go.opentelemetry.io/otel/trace. To read more about metrics, see go.opentelemetry.io/otel/metric. To read more about logs, see go.opentelemetry.io/otel/log. To read more about propagation, see go.opentelemetry.io/otel/propagation and go.opentelemetry.io/otel/baggage.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:37:33.097Z (about 1 month ago)
• Versions: 78
• Dependent Packages: 0
• Dependent Repositories: 1
• Rankings:
  • Forks count: 0.935%
  • Stargazers count: 1.099%
  • Average: 3.82%
  • Dependent repos count: 4.794%
  • Dependent packages count: 8.453%

go: github.com/open-telemetry/opentelemetry-go/exporters/otlp

Deprecated: This package was moved to exporters/otlp/otlptrace and exporters/otlp/otlpmetric.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/otlp#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.20.1 (published almost 2 years ago)
• Last Synced: 2024-11-11T01:37:04.325Z (about 1 month ago)
• Versions: 22
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.628%
  • Stargazers count: 0.655%
  • Average: 4.407%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporters/otlp/otlptrace

Package otlptrace contains abstractions for OTLP span exporters. See the official OTLP span exporter implementations:

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/otlp/otlptrace#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:37:21.285Z (about 1 month ago)
• Versions: 50
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.632%
  • Stargazers count: 0.679%
  • Average: 4.414%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporters/otlp/otlptrace/otlptracehttp

Package otlptracehttp provides an OTLP span exporter using HTTP with protobuf payloads. By default the telemetry is sent to https://localhost:4318/v1/traces. Exporter should be created using New. The environment variables described below can be used for configuration. OTEL_EXPORTER_OTLP_ENDPOINT (default: "https://localhost:4318") - target base URL ("/v1/traces" is appended) to which the exporter sends telemetry. The value must contain a scheme ("http" or "https") and host. The value may additionally contain a port and a path. The value should not contain a query string or fragment. The configuration can be overridden by OTEL_EXPORTER_OTLP_TRACES_ENDPOINT environment variable and by WithEndpoint, WithEndpointURL, WithInsecure options. OTEL_EXPORTER_OTLP_TRACES_ENDPOINT (default: "https://localhost:4318/v1/traces") - target URL to which the exporter sends telemetry. The value must contain a scheme ("http" or "https") and host. The value may additionally contain a port and a path. The value should not contain a query string or fragment. The configuration can be overridden by WithEndpoint, WithEndpointURL, WithInsecure, and WithURLPath options. OTEL_EXPORTER_OTLP_HEADERS, OTEL_EXPORTER_OTLP_TRACES_HEADERS (default: none) - key-value pairs used as headers associated with HTTP requests. The value is expected to be represented in a format matching the W3C Baggage HTTP Header Content Format, except that additional semi-colon delimited metadata is not supported. Example value: "key1=value1,key2=value2". OTEL_EXPORTER_OTLP_TRACES_HEADERS takes precedence over OTEL_EXPORTER_OTLP_HEADERS. The configuration can be overridden by WithHeaders option. OTEL_EXPORTER_OTLP_TIMEOUT, OTEL_EXPORTER_OTLP_TRACES_TIMEOUT (default: "10000") - maximum time in milliseconds the OTLP exporter waits for each batch export. OTEL_EXPORTER_OTLP_TRACES_TIMEOUT takes precedence over OTEL_EXPORTER_OTLP_TIMEOUT. The configuration can be overridden by WithTimeout option. OTEL_EXPORTER_OTLP_COMPRESSION, OTEL_EXPORTER_OTLP_TRACES_COMPRESSION (default: none) - the compression strategy the exporter uses to compress the HTTP body. Supported value: "gzip". OTEL_EXPORTER_OTLP_TRACES_COMPRESSION takes precedence over OTEL_EXPORTER_OTLP_COMPRESSION. The configuration can be overridden by WithCompression option. OTEL_EXPORTER_OTLP_CERTIFICATE, OTEL_EXPORTER_OTLP_TRACES_CERTIFICATE (default: none) - the filepath to the trusted certificate to use when verifying a server's TLS credentials. OTEL_EXPORTER_OTLP_TRACES_CERTIFICATE takes precedence over OTEL_EXPORTER_OTLP_CERTIFICATE. The configuration can be overridden by WithTLSClientConfig option. OTEL_EXPORTER_OTLP_CLIENT_CERTIFICATE, OTEL_EXPORTER_OTLP_TRACES_CLIENT_CERTIFICATE (default: none) - the filepath to the client certificate/chain trust for client's private key to use in mTLS communication in PEM format. OTEL_EXPORTER_OTLP_TRACES_CLIENT_CERTIFICATE takes precedence over OTEL_EXPORTER_OTLP_CLIENT_CERTIFICATE. The configuration can be overridden by WithTLSClientConfig option. OTEL_EXPORTER_OTLP_CLIENT_KEY, OTEL_EXPORTER_OTLP_TRACES_CLIENT_KEY (default: none) - the filepath to the client's private key to use in mTLS communication in PEM format. OTEL_EXPORTER_OTLP_TRACES_CLIENT_KEY takes precedence over OTEL_EXPORTER_OTLP_CLIENT_KEY. The configuration can be overridden by WithTLSClientConfig option.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/otlp/otlptrace/otlptracehttp#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:36:59.261Z (about 1 month ago)
• Versions: 50
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.632%
  • Stargazers count: 0.679%
  • Average: 4.414%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: go.opentelemetry.io/otel/internal/tools

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/internal/tools#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.0.0-20240123221504-cef39a1e17be (published 11 months ago)
• Last Synced: 2024-11-10T01:09:31.087Z (about 1 month ago)
• Versions: 184
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.656%
  • Stargazers count: 0.717%
  • Average: 4.429%
  • Dependent packages count: 6.998%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/sdk

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/sdk#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:37:39.633Z (about 1 month ago)
• Versions: 61
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.656%
  • Stargazers count: 0.717%
  • Average: 4.429%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporters/prometheus

Package prometheus provides a Prometheus Exporter that converts OTLP metrics into the Prometheus exposition format and implements prometheus.Collector to provide a handler for these metrics.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/prometheus#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.48.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:37:40.966Z (about 1 month ago)
• Versions: 44
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.656%
  • Stargazers count: 0.717%
  • Average: 4.429%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: go.opentelemetry.io/otel/example/prom-collector

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/example/prom-collector#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.20.1 (published almost 2 years ago)
• Last Synced: 2024-11-14T07:01:32.095Z (about 1 month ago)
• Versions: 6
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.656%
  • Stargazers count: 0.717%
  • Average: 4.429%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/bridge/opentracing

Package opentracing implements a bridge that forwards OpenTracing API calls to the OpenTelemetry SDK. To use the bridge, first create an OpenTelemetry tracer of choice. Then use the NewTracerPair() function to create two tracers - one implementing OpenTracing API (BridgeTracer) and one that implements the OpenTelemetry API (WrapperTracer) and mostly forwards the calls to the OpenTelemetry tracer of choice, but does some extra steps to make the interaction between both APIs working. If the OpenTelemetry tracer of choice already knows how to cooperate with OpenTracing API through the OpenTracing bridge (explained in detail below), then it is fine to skip the WrapperTracer by calling the NewBridgeTracer() function to get the bridge tracer and then passing the chosen OpenTelemetry tracer to the SetOpenTelemetryTracer() function of the bridge tracer. To use an OpenTelemetry span as the parent of an OpenTracing span, create a context using the ContextWithBridgeSpan() function of the bridge tracer, and then use the StartSpanFromContext function of the OpenTracing API. Bridge tracer also allows the user to install a warning handler through the SetWarningHandler() function. The warning handler will be called when there is some misbehavior of the OpenTelemetry tracer with regard to the cooperation with the OpenTracing API. For an OpenTelemetry tracer to cooperate with OpenTracing API through the BridgeTracer, the OpenTelemetry tracer needs to (reasoning is below the list): 1. Return the same context it received in the Start() function if migration.SkipContextSetup() returns true. 2. Implement the migration.DeferredContextSetupTracerExtension interface. The implementation should setup the context it would normally do in the Start() function if the migration.SkipContextSetup() function returned false. Calling ContextWithBridgeSpan() is not necessary. 3. Have an access to the BridgeTracer instance. 4. If the migration.SkipContextSetup() function returned false, the tracer should use the ContextWithBridgeSpan() function to install the created span as an active OpenTracing span. There are some differences between OpenTracing and OpenTelemetry APIs, especially with regard to Go context handling. When a span is created with an OpenTracing API (through the StartSpan() function) the Go context is not available. BridgeTracer has access to the OpenTelemetry tracer of choice, so in the StartSpan() function BridgeTracer translates the parameters to the OpenTelemetry version and uses the OpenTelemetry tracer's Start() function to actually create a span. The OpenTelemetry Start() function takes the Go context as a parameter, so BridgeTracer at this point passes a temporary context to Start(). All the changes to the temporary context will be lost at the end of the StartSpan() function, so the OpenTelemetry tracer of choice should not do anything with the context. If the returned context is different, BridgeTracer will warn about it. The OpenTelemetry tracer of choice can learn about this situation by using the migration.SkipContextSetup() function. The tracer will receive an opportunity to set up the context at a later stage. Usually after StartSpan() is finished, users of the OpenTracing API are calling (either directly or through the opentracing.StartSpanFromContext() helper function) the opentracing.ContextWithSpan() function to insert the created OpenTracing span into the context. At that time, the OpenTelemetry tracer of choice has a chance of setting up the context through a hook invoked inside the opentracing.ContextWithSpan() function. For that to happen, the tracer should implement the migration.DeferredContextSetupTracerExtension interface. This so far explains the need for points 1. and 2. When the span is created with the OpenTelemetry API (with the Start() function) then migration.SkipContextSetup() will return false. This means that the tracer can do the usual setup of the context, but it also should set up the active OpenTracing span in the context. This is because OpenTracing API is not used at all in the creation of the span, but the OpenTracing API may be used during the time when the created OpenTelemetry span is current. For this case to work, we need to also set up active OpenTracing span in the context. This can be done with the ContextWithBridgeSpan() function. This means that the OpenTelemetry tracer of choice needs to have an access to the BridgeTracer instance. This should explain the need for points 3. and 4. Another difference related to the Go context handling is in logging - OpenTracing API does not take a context parameter in the LogFields() function, so when the call to the function gets translated to OpenTelemetry AddEvent() function, an empty context is passed.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/bridge/opentracing#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:36:55.976Z (about 1 month ago)
• Versions: 60
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.656%
  • Stargazers count: 0.717%
  • Average: 4.429%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporters/jaeger

Package jaeger contains an OpenTelemetry tracing exporter for Jaeger. Deprecated: This module is no longer supported. OpenTelemetry dropped support for Jaeger exporter in July 2023. Jaeger officially accepts and recommends using OTLP. Use go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp or go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc instead.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/jaeger#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.17.0 (published over 1 year ago)
• Last Synced: 2024-11-11T01:36:43.871Z (about 1 month ago)
• Versions: 32
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.656%
  • Stargazers count: 0.717%
  • Average: 4.429%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: go.opentelemetry.io/otel/bridge/opencensus/opencensusmetric

Package opencensusmetric provides a metric bridge from OpenCensus to OpenTelemetry.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/bridge/opencensus/opencensusmetric#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.0.0-20220920002240-b6d4335a7225 (published over 2 years ago)
• Last Synced: 2024-11-10T01:09:23.627Z (about 1 month ago)
• Versions: 2
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.656%
  • Stargazers count: 0.717%
  • Average: 4.429%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporters/trace/stackdriver

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/trace/stackdriver#section-documentation
• Licenses: apache-2.0
• Latest release: v0.2.3 (published almost 5 years ago)
• Last Synced: 2024-11-11T01:37:40.485Z (about 1 month ago)
• Versions: 1
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.646%
  • Stargazers count: 0.98%
  • Average: 4.493%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/example/passthrough

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/example/passthrough#section-documentation
• Licenses: apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:37:03.924Z (about 1 month ago)
• Versions: 49
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.646%
  • Stargazers count: 0.98%
  • Average: 4.493%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/example/opencensus

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/example/opencensus#section-documentation
• Licenses: apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:36:55.989Z (about 1 month ago)
• Versions: 48
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.646%
  • Stargazers count: 0.98%
  • Average: 4.493%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/bridge/opencensus/test

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/bridge/opencensus/test#section-documentation
• Licenses: apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:37:22.914Z (about 1 month ago)
• Versions: 42
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.646%
  • Stargazers count: 0.98%
  • Average: 4.493%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/example/fib

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/example/fib#section-documentation
• Licenses: apache-2.0
• Latest release: v1.20.0 (published about 1 year ago)
• Last Synced: 2024-11-11T01:36:47.540Z (about 1 month ago)
• Versions: 34
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.646%
  • Stargazers count: 0.98%
  • Average: 4.493%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/bridge/opencensus/examples/bridge

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/bridge/opencensus/examples/bridge#section-documentation
• Licenses: apache-2.0
• Latest release: v0.14.0 (published about 4 years ago)
• Last Synced: 2024-11-11T01:36:46.011Z (about 1 month ago)
• Versions: 1
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.646%
  • Stargazers count: 0.98%
  • Average: 4.493%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/example/view

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/example/view#section-documentation
• Licenses: apache-2.0
• Latest release: v0.43.0 (published about 1 year ago)
• Last Synced: 2024-11-11T01:36:48.424Z (about 1 month ago)
• Versions: 18
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.646%
  • Stargazers count: 0.98%
  • Average: 4.493%
  • Dependent packages count: 6.999%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/example/dice

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/example/dice#section-documentation
• Licenses: apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:37:36.743Z (about 1 month ago)
• Versions: 15
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.889%
  • Stargazers count: 1.02%
  • Average: 5.381%
  • Dependent packages count: 8.907%
  • Dependent repos count: 10.707%

go: github.com/open-telemetry/opentelemetry-go/bridge/opentracing/test

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/bridge/opentracing/test#section-documentation
• Licenses: apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:37:00.975Z (about 1 month ago)
• Versions: 26
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Forks count: 0.889%
  • Stargazers count: 1.02%
  • Average: 5.381%
  • Dependent packages count: 8.907%
  • Dependent repos count: 10.707%

go: github.com/open-telemetry/opentelemetry-go/exporters/otlp/otlplog/otlploggrpc

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/otlp/otlplog/otlploggrpc#section-documentation
• Licenses: apache-2.0
• Latest release:
• Last Synced: 2024-11-11T01:36:44.619Z (about 1 month ago)
• Versions: 4
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.283%
  • Average: 6.493%
  • Dependent repos count: 6.704%

go: github.com/open-telemetry/opentelemetry-go/exporters/stdout/stdoutlog

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/stdout/stdoutlog#section-documentation
• Licenses: apache-2.0
• Latest release:
• Last Synced: 2024-11-11T01:37:31.828Z (about 1 month ago)
• Versions: 7
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.308%
  • Average: 6.521%
  • Dependent repos count: 6.734%

go: github.com/open-telemetry/opentelemetry-go/exporters/otlp/otlplog/otlploghttp

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/otlp/otlplog/otlploghttp#section-documentation
• Licenses: apache-2.0
• Latest release:
• Last Synced: 2024-11-11T01:37:05.918Z (about 1 month ago)
• Versions: 7
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.368%
  • Average: 6.582%
  • Dependent repos count: 6.797%

go: go.opentelemetry.io/otel/exporters

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/exporters#section-documentation
• Licenses: Apache-2.0
• Latest release:
• Last Synced: 2024-11-10T01:09:46.713Z (about 1 month ago)
• Versions: 0
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.437%
  • Average: 6.655%
  • Dependent repos count: 6.872%

go: go.opentelemetry.io/contrib/samplers

Package otel provides global access to the OpenTelemetry API. The subpackages of the otel package provide an implementation of the OpenTelemetry API. The provided API is used to instrument code and measure data about that code's performance and operation. The measured data, by default, is not processed or transmitted anywhere. An implementation of the OpenTelemetry SDK, like the default SDK implementation (go.opentelemetry.io/otel/sdk), and associated exporters are used to process and transport this data. To read the getting started guide, see https://opentelemetry.io/docs/languages/go/getting-started/. To read more about tracing, see go.opentelemetry.io/otel/trace. To read more about metrics, see go.opentelemetry.io/otel/metric. To read more about logs, see go.opentelemetry.io/otel/log. To read more about propagation, see go.opentelemetry.io/otel/propagation and go.opentelemetry.io/otel/baggage.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/contrib/samplers#section-documentation
• Licenses: Apache-2.0
• Latest release:
• Last Synced: 2024-11-11T01:36:44.578Z (about 1 month ago)
• Versions: 0
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.437%
  • Average: 6.655%
  • Dependent repos count: 6.872%

go: go.opentelemetry.io/contrib/instrumentation

Package otel provides global access to the OpenTelemetry API. The subpackages of the otel package provide an implementation of the OpenTelemetry API. The provided API is used to instrument code and measure data about that code's performance and operation. The measured data, by default, is not processed or transmitted anywhere. An implementation of the OpenTelemetry SDK, like the default SDK implementation (go.opentelemetry.io/otel/sdk), and associated exporters are used to process and transport this data. To read the getting started guide, see https://opentelemetry.io/docs/languages/go/getting-started/. To read more about tracing, see go.opentelemetry.io/otel/trace. To read more about metrics, see go.opentelemetry.io/otel/metric. To read more about logs, see go.opentelemetry.io/otel/log. To read more about propagation, see go.opentelemetry.io/otel/propagation and go.opentelemetry.io/otel/baggage.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/contrib/instrumentation#section-documentation
• Licenses: Apache-2.0
• Latest release:
• Last Synced: 2024-11-11T01:36:52.129Z (about 1 month ago)
• Versions: 0
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.437%
  • Average: 6.655%
  • Dependent repos count: 6.872%

go: github.com/open-telemetry/opentelemetry-go/sdk/log

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/sdk/log#section-documentation
• Licenses: apache-2.0
• Latest release: v0.2.0-alpha (published 8 months ago)
• Last Synced: 2024-11-11T01:36:53.437Z (about 1 month ago)
• Versions: 7
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.992%
  • Average: 7.439%
  • Dependent repos count: 7.886%

go: github.com/open-telemetry/opentelemetry-go/log

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/log#section-documentation
• Licenses: apache-2.0
• Latest release: v0.1.0-alpha (published 9 months ago)
• Last Synced: 2024-11-11T01:37:41.285Z (about 1 month ago)
• Versions: 9
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.998%
  • Average: 7.446%
  • Dependent repos count: 7.893%

go: github.com/open-telemetry/opentelemetry-go/exporters/otlp/internal/retry

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/otlp/internal/retry#section-documentation
• Licenses: apache-2.0
• Latest release: v1.17.0 (published over 1 year ago)
• Last Synced: 2024-11-11T01:37:11.166Z (about 1 month ago)
• Versions: 25
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/example/otel-collector

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/example/otel-collector#section-documentation
• Licenses: apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:36:42.101Z (about 1 month ago)
• Versions: 64
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: go.opentelemetry.io/otel/bridge/opencensus/examples/bridge

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/go.opentelemetry.io/otel/bridge/opencensus/examples/bridge#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.14.0 (published about 4 years ago)
• Last Synced: 2024-11-27T07:25:01.353Z (24 days ago)
• Versions: 1
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/example/namedtracer

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/example/namedtracer#section-documentation
• Licenses: apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:36:43.314Z (about 1 month ago)
• Versions: 72
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/trace

Package trace provides an implementation of the tracing part of the OpenTelemetry API. To participate in distributed traces a Span needs to be created for the operation being performed as part of a traced workflow. In its simplest form: A Tracer is unique to the instrumentation and is used to create Spans. Instrumentation should be designed to accept a TracerProvider from which it can create its own unique Tracer. Alternatively, the registered global TracerProvider from the go.opentelemetry.io/otel package can be used as a default. This package does not conform to the standard Go versioning policy; all of its interfaces may have methods added to them without a package major version bump. This non-standard API evolution could surprise an uninformed implementation author. They could unknowingly build their implementation in a way that would result in a runtime panic for their users that update to the new API. The API is designed to help inform an instrumentation author about this non-standard API evolution. It requires them to choose a default behavior for unimplemented interface methods. There are three behavior choices they can make: All interfaces in this API embed a corresponding interface from go.opentelemetry.io/otel/trace/embedded. If an author wants the default behavior of their implementations to be a compilation failure, signaling to their users they need to update to the latest version of that implementation, they need to embed the corresponding interface from go.opentelemetry.io/otel/trace/embedded in their implementation. For example, If an author wants the default behavior of their implementations to panic, they can embed the API interface directly. This option is not recommended. It will lead to publishing packages that contain runtime panics when users update to newer versions of go.opentelemetry.io/otel/trace, which may be done with a transitive dependency. Finally, an author can embed another implementation in theirs. The embedded implementation will be used for methods not defined by the author. For example, an author who wants to default to silently dropping the call can use go.opentelemetry.io/otel/trace/noop: It is strongly recommended that authors only embed go.opentelemetry.io/otel/trace/noop if they choose this default behavior. That implementation is the only one OpenTelemetry authors can guarantee will fully implement all the API interfaces when a user updates their API.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/trace#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:36:41.508Z (about 1 month ago)
• Versions: 54
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/oteltest

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/oteltest#section-documentation
• Licenses: apache-2.0
• Latest release: v0.20.1 (published almost 2 years ago)
• Last Synced: 2024-11-11T01:37:18.607Z (about 1 month ago)
• Versions: 8
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporters/otlp/otlpmetric/otlpmetricgrpc

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/otlp/otlpmetric/otlpmetricgrpc#section-documentation
• Licenses: apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:36:37.546Z (about 1 month ago)
• Versions: 45
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporters/zipkin

Package zipkin contains an OpenTelemetry tracing exporter for Zipkin.

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/zipkin#section-documentation
• Licenses: Apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:37:26.084Z (about 1 month ago)
• Versions: 50
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/internal/metric

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/internal/metric#section-documentation
• Licenses: apache-2.0
• Latest release: v0.27.0 (published almost 3 years ago)
• Last Synced: 2024-11-11T01:36:45.292Z (about 1 month ago)
• Versions: 7
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/example/prom-collector

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/example/prom-collector#section-documentation
• Licenses: apache-2.0
• Latest release: v0.20.1 (published almost 2 years ago)
• Last Synced: 2024-11-11T01:36:45.745Z (about 1 month ago)
• Versions: 6
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporters/trace/jaeger

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/trace/jaeger#section-documentation
• Licenses: apache-2.0
• Latest release: v0.20.1 (published almost 2 years ago)
• Last Synced: 2024-11-11T01:36:46.382Z (about 1 month ago)
• Versions: 24
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporters/stdout

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/stdout#section-documentation
• Licenses: apache-2.0
• Latest release: v0.20.1 (published almost 2 years ago)
• Last Synced: 2024-11-11T01:36:46.749Z (about 1 month ago)
• Versions: 12
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporters/trace/zipkin

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/trace/zipkin#section-documentation
• Licenses: apache-2.0
• Latest release: v0.20.1 (published almost 2 years ago)
• Last Synced: 2024-11-11T01:36:46.854Z (about 1 month ago)
• Versions: 23
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporter/metric/prometheus

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporter/metric/prometheus#section-documentation
• Licenses: apache-2.0
• Latest release: v0.2.1 (published almost 5 years ago)
• Last Synced: 2024-11-11T01:36:47.853Z (about 1 month ago)
• Versions: 2
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/sdk/export/metric

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/sdk/export/metric#section-documentation
• Licenses: apache-2.0
• Latest release: v0.28.0 (published over 2 years ago)
• Last Synced: 2024-11-11T01:36:50.062Z (about 1 month ago)
• Versions: 12
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/bridge/opencensus

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/bridge/opencensus#section-documentation
• Licenses: apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:36:50.205Z (about 1 month ago)
• Versions: 51
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporters/stdout/stdoutmetric

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/stdout/stdoutmetric#section-documentation
• Licenses: apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:36:53.895Z (about 1 month ago)
• Versions: 45
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporters/stdout/stdouttrace

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/stdout/stdouttrace#section-documentation
• Licenses: apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:36:54.229Z (about 1 month ago)
• Versions: 50
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporters/otlp/otlptrace/otlptracegrpc

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/otlp/otlptrace/otlptracegrpc#section-documentation
• Licenses: apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:36:55.605Z (about 1 month ago)
• Versions: 50
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/example/grpc

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/example/grpc#section-documentation
• Licenses: apache-2.0
• Latest release: v0.10.0 (published over 4 years ago)
• Last Synced: 2024-11-11T01:37:03.175Z (about 1 month ago)
• Versions: 13
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/example/zipkin

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/example/zipkin#section-documentation
• Licenses: apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:37:05.155Z (about 1 month ago)
• Versions: 70
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporters/otlp/otlpmetric/otlpmetrichttp

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporters/otlp/otlpmetric/otlpmetrichttp#section-documentation
• Licenses: apache-2.0
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:37:31.451Z (about 1 month ago)
• Versions: 44
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/schema

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/schema#section-documentation
• Licenses: apache-2.0
• Latest release: v0.0.8 (published 9 months ago)
• Last Synced: 2024-11-11T01:36:50.867Z (about 1 month ago)
• Versions: 11
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/example/http

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/example/http#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.10.0 (published over 4 years ago)
• Last Synced: 2024-11-11T01:37:34.212Z (about 1 month ago)
• Versions: 13
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/example/basic

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/example/basic#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.15.0 (published about 4 years ago)
• Last Synced: 2024-11-11T01:37:36.350Z (about 1 month ago)
• Versions: 18
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/example/jaeger

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/example/jaeger#section-documentation
• Licenses: apache-2.0
• Latest release: v1.17.0 (published over 1 year ago)
• Last Synced: 2024-11-11T01:37:37.460Z (about 1 month ago)
• Versions: 55
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/exporter/trace/jaeger

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/exporter/trace/jaeger#section-documentation
• Licenses: apache-2.0
• Latest release: v0.2.1 (published almost 5 years ago)
• Last Synced: 2024-11-11T01:37:38.318Z (about 1 month ago)
• Versions: 5
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-telemetry/opentelemetry-go/example/prometheus

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/example/prometheus#section-documentation
• Licenses: apache-2.0
• Latest release: v0.48.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:37:39.780Z (about 1 month ago)
• Versions: 66
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 6.999%
  • Average: 8.173%
  • Dependent repos count: 9.346%

go: github.com/open-teLemetry/opentelemetry-go

• Homepage:
• Documentation: https://pkg.go.dev/github.com/open-teLemetry/opentelemetry-go#section-documentation
• Licenses:
• Latest release: v1.26.0 (published 8 months ago)
• Last Synced: 2024-11-11T01:37:36.978Z (about 1 month ago)
• Versions: 78
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 7.576%
  • Average: 8.47%
  • Dependent repos count: 9.364%

go: github.com/open-telemetry/opentelemetry-go/experimental/streaming/example/basic

• Homepage: https://github.com/open-telemetry/opentelemetry-go
• Documentation: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-go/experimental/streaming/example/basic#section-documentation
• Licenses: Apache-2.0
• Latest release: v0.0.0-20191017054958-5e409de1aa9b (published about 5 years ago)
• Last Synced: 2024-11-10T01:09:07.396Z (about 1 month ago)
• Versions: 6
• Dependent Packages: 0
• Dependent Repositories: 0
• Rankings:
  • Dependent packages count: 9.303%
  • Average: 9.896%
  • Dependent repos count: 10.489%