Resource attribute

What Resource attribute shows

Resource attribute is metadata identifying the entity that produced telemetry, such as service, host, process, or environment. It matters when a team can state the decision the evidence should support, the population being measured, and the time window in which the observation matters. That framing keeps a familiar label from becoming a dashboard tile with no operational meaning. The collection method and owner should be visible whenever the signal is used in a review.

A concrete example

Service name, version, namespace, and environment distinguish deployments during a rollout. A useful workflow records relevant context, compares the observation with an appropriate baseline, and follows the evidence to the service or change that may explain it. The signal should start a question rather than close the investigation. Teams should also record what action follows a meaningful change and how the result will be checked.

Limitations and tradeoffs

Incorrect identity fragments services, while secrets and request values do not belong in resource identity. Interpret resource attribute alongside related signals and explicit service objectives. Sampling, aggregation, clock behavior, retention, and access policy can all affect what an operator sees. When those details are missing, conclusions should remain provisional and a precise-looking value should not be presented as a complete account of user experience.