Resource attributes connect application spans to the environment where work ran. When spans include consistent resource metadata, OpsRamp can group trace behavior by service and infrastructure context and show related topology or resource views.

Useful resource context

For Kubernetes workloads, common correlation fields include cluster, namespace, deployment, pod, and container identity. For other environments, use stable host, service instance, cloud, or deployment attributes supported by your instrumentation.

Investigate an affected resource

1. Open the trace and select the slow or failed span.
2. Review its service and resource attributes.
3. Open the available infrastructure or topology view for the same time range.
4. Locate the matching workload or resource and compare its state and metrics with the span interval.
5. Check neighboring services and dependencies when several resources show the same symptom.

When a resource is not linked

A trace can remain searchable even when it does not include enough resource metadata for correlation. Confirm that resource attributes are set consistently at process startup and that identifiers match the resources known to OpsRamp. Avoid using ephemeral values as the primary service identity.

Resource metadata describes where a span was produced; it does not ensure that the resource caused the failure. Combine it with span timing, dependency behavior, logs, and resource metrics.