fastports

opentelemetry-registry 0.5.0

devel/rubygem-opentelemetry-registry

Registry for the OpenTelemetry Instrumentation libraries

Category
devel
Maintainer
sunpoet@FreeBSD.org
WWW
https://opentelemetry.io/ https://github.com/open-telemetry/opentelemetry-ruby/tree/main/registry https://github.com/open-telemetry/opentelemetry-ruby
License
APACHE20
USES
gem

Description

The instrumentation Registry contains information about available
instrumentation, facilitates discovery, installation, and configuration.

The Registry allows for instrumentation to avoid depending directly on a
specific SDK implementation.

The SDK depends on the Registry, the instrumentation Base class depends on the
Registry, and auto instrumentation libraries extend the instrumentation Base
class.

The motivation for decoupling the Registry (and by extension the
instrumentation) from a specific SDK implementation means that anyone can
implement their own OpenTelemetry API compatible SDK, and they could continue to
use community made instrumentation.

Dependencies

Commit History

may be incomplete — full history at freebsd-ports on GitHub

Commit Credits Log message
0.4.0
bf0e6b9c5b files touched
Po-Chuan Hsieh (sunpoet)
devel/rubygem-opentelemetry-registry: Update WWW
0.4.0
da41f55698 files touched
Po-Chuan Hsieh (sunpoet)
devel/rubygem-opentelemetry-registry: Update to 0.4.0
Changes:	https://github.com/open-telemetry/opentelemetry-ruby/releases
		https://github.com/open-telemetry/opentelemetry-ruby/blob/main/registry/CHANGELOG.md
0.3.1
a4c6176889 files touched
Po-Chuan Hsieh (sunpoet)
devel/rubygem-opentelemetry-registry: Update to 0.3.1
Changes:	https://github.com/open-telemetry/opentelemetry-ruby/releases
		https://github.com/open-telemetry/opentelemetry-ruby/blob/main/registry/CHANGELOG.md
0.3.0
53adcca119 files touched
Po-Chuan Hsieh (sunpoet)
devel/rubygem-opentelemetry-registry: Add rubygem-opentelemetry-registry 0.3.0
The instrumentation Registry contains information about available
instrumentation, facilitates discovery, installation, and configuration.

The Registry allows for instrumentation to avoid depending directly on a
specific SDK implementation.

The SDK depends on the Registry, the instrumentation Base class depends on the
Registry, and auto instrumentation libraries extend the instrumentation Base
class.

The motivation for decoupling the Registry (and by extension the
instrumentation) from a specific SDK implementation means that anyone can
implement their own OpenTelemetry API compatible SDK, and they could continue to
use community made instrumentation.