New

The executive guide to generative AI

Read more
About usPartnersSupport|Login
IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Limitations Manage storage »
Elastic Docs ›Elastic Observability [8.15] ›Application performance monitoring (APM) ›Use OpenTelemetry with APM

Resource attributes

edit

Resource attributes

edit

A resource attribute is a key/value pair containing information about the entity producing telemetry. Resource attributes are mapped to Elastic Common Schema (ECS) fields like service.*, cloud.*, process.*, etc. These fields describe the service and the environment that the service runs in.

The examples shown here set the Elastic (ECS) service.environment field for the resource, i.e. service, that is producing trace events. Note that Elastic maps the OpenTelemetry deployment.environment field to the ECS service.environment field on ingestion.

OpenTelemetry agent

Use the OTEL_RESOURCE_ATTRIBUTES environment variable to pass resource attributes at process invocation.

export OTEL_RESOURCE_ATTRIBUTES=deployment.environment=production

OpenTelemetry collector

Use the resource processor to set or apply changes to resource attributes.

...
processors:
  resource:
    attributes:
    - key: deployment.environment
      action: insert
      value: production
...

Need to add event attributes instead? Use attributes—​not to be confused with resource attributes—​to add data to span, log, or metric events. Attributes can be added as a part of the OpenTelemetry instrumentation process or with the attributes processor.

Elastic integrates with OpenTelemetry, allowing you to reuse your existing instrumentation to easily send observability data to the Elastic Stack.

For more information on how to combine Elastic and OpenTelemetry, see OpenTelemetry integration.

« Limitations Manage storage »
Was this helpful?
Feedback