proxy.golang.org : 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.

Registry - Homepage - Documentation - JSON
purl: pkg:golang/go.opentelemetry.io/otel/sdk/metric
Keywords: logging , metrics , opentelemetry , tracing
License: Apache-2.0
Latest release: about 1 month ago
First release: over 4 years ago
Namespace: go.opentelemetry.io/otel/sdk
Dependent packages: 3,173
Dependent repositories: 15,074
Stars: 5,262 on GitHub
Forks: 1,069 on GitHub
Docker dependents: 1,129
Docker downloads: 9,928,066,202
Total Commits: 1917
Committers: 276
Average commits per author: 6.946
Development Distribution Score (DDS): 0.773
More commit stats: commits.ecosyste.ms
See more repository details: repos.ecosyste.ms
Last synced: about 18 hours ago

• Readme
• Versions 54
• Dependent Packages 3,173
• Maintainers 0