Skip to content

Latest commit

 

History

History
78 lines (53 loc) · 3.04 KB

sdk-resource.md

File metadata and controls

78 lines (53 loc) · 3.04 KB
Raw

Resource SDK

A Resource represents the entity producing telemetry. The primary purpose of resources as a first-class concept in the API is decoupling of discovery of resource information from exporters. This allows for independent development and easy customization for users that need to integrate with closed source environments. API MUST allow for creation of Resources and for associating them with telemetry.

When used with distributed tracing, a resource can be associated with the TracerSdk. When associated with TracerSdk, all Spans produced by the Tracer, that is implemented by this TracerSdk, will automatically be associated with this Resource.

When used with metrics, a resource can be associated with the MeterSdk. When associated with MeterSdk, all Metrics produced by this Meter, that is implemented by this MeterSdk, will automatically be associated with this Resource.

Resource creation

The API interface must support two ways to instantiate new resources. Those are:

Create

The interface MUST provide a way to create a new resource, from a collection of attributes. Examples include a factory method or a constructor for a resource object. A factory method is recommended to enable support for cached objects.

Required parameters:

  • a collection of name/value attributes, where name is a string and value can be one of: string, int64, double, bool.

Merge

The interface MUST provide a way for a primary resource to merge with a secondary resource, resulting in the creation of a brand new resource. The original resources should be unmodified.

This is utilized for merging of resources whose attributes come from different sources, such as environment variables, or metadata extracted from the host or container.

Already set attributes MUST NOT be overwritten unless they are the empty string.

Attribute key namespacing SHOULD be used to prevent collisions across different resource detection steps.

Required parameters:

  • the primary resource whose attributes takes precedence.
  • the secondary resource whose attributes will be merged.

The empty resource

It is recommended, but not required, to provide a way to quickly create an empty resource.

Note that the OpenTelemetry project documents certain "standard attributes" that have prescribed semantic meanings.

Resource operations

In addition to resource creation, the following operations should be provided:

Retrieve attributes

The API should provide a way to retrieve a read only collection of attributes associated with a resource. The attributes should consist of the name and values, both of which should be strings.

There is no need to guarantee the order of the attributes.

The most common operation when retrieving attributes is to enumerate over them. As such, it is recommended to optimize the resulting collection for fast enumeration over other considerations such as a way to quickly retrieve a value for a attribute with a specific key.