Versions Compared

Old Version 5

changes.mady.by.user Shrey Amin

Saved on

compared with

New Version 6

changes.mady.by.user Shrey Amin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Resource Attribute Name

Comments

Set By

1service.name

User configurable using the otel_service_name option for UAG and OMS, and otel_uip_service_name for Universal Extensions.

  • OMS
  • UAG
  • Universal Extensions
2service.version

Not configurable. Automatically set according to the UAG and OMS version. For Universal Extensions, value is set to the Extension version defined in extension.yml

  • UAG
  • OMS
  • Universal Extensions
3service.namespace

Not configurable. Always Stonebranch.UAC

  • UAG
  • OMS
  • Universal Extensions
4service.port

Only set for OMS – the service port used by UAG and Controller to connect to OMS.

  • OMS
5service.instance.id

Value will be: <hostname>:<brokerport>

For instance, if the hostname is sbus44 and broker is running on port 7887 then the value will be sbus44:7887. This value is unique enough to distinguish multiple instances of UAG and OMS.

  • UAG
  • OMS
  • Universal Extensions
6host.name

Not configurable.

  • UAG
  • OMS
  • Universal Extensions
7os.name

Not configurable.

  • UAG
  • OMS
  • Universal Extensions
8os.version

Not configurable.

  • UAG
  • OMS
  • Universal Extensions
9process.owner

Not configurable.

  • UAG
  • OMS
  • Universal Extensions
10process.pid

Not configurable.

  • UAG
  • OMS
  • Universal Extensions
11process.executable.path

Not configurable.

  • Universal Extensions
12process.runtime.version

Not configurable.

  • Universal Extensions
13agent.id

Set to the Agent netname.

  • UAG
  • Universal Extensions
14task.name

The name of the launched task.

  • Universal Extensions
15security.business.services

Comma-separated string specifying the business services the task is part of.

  • Universal Extensions

By default, the attributes listed above will not be added to the final, exported metrics (to avoid high-cardinality issues). The Opentelemetry Collector must be configured to copy the resource attributes as normal labels. The snippet below shows how to use the Opentelemetry Collector Transform Processor to do this:

Code Block
languagepy
titleconfig.yaml
collapsetrue
processors:
    transform:
    metric_statements:
        - context: datapoint
          statements:
          # Only business_services is added in this example
          - set(attributes["security.business.services"], resource.attributes["security.business.services"])
          
service:
  pipelines:
    metrics:
      receivers: [otlp, opencensus]
      processors: [transform, batch]
      exporters: [prometheus]