OpsRamp uses service, resource, and operation identity to organize spans and connect application behavior to the environment where it occurred.

Service

A service is a logical application component such as an API, worker, checkout service, or payment service. OpenTelemetry commonly identifies it with the service.name resource attribute. Use stable, meaningful names across deployments so spans aggregate into the correct service view.

Resource

A resource describes the entity that produced telemetry. It can identify a process, host, virtual machine, container, Kubernetes pod, namespace, cluster, deployment, cloud account, or region. Resource attributes apply to all spans emitted by that resource.
OpsRamp can use infrastructure-oriented resource attributes to correlate trace behavior with runtime context. Kubernetes attributes, for example, can connect a slow operation to a cluster, namespace, workload, or deployment.

Operation

An operation is the named activity represented by a span. Examples include an HTTP route, RPC method, database call, queue receive operation, or internal processing step. Operation names should describe a bounded class of work and avoid unbounded values such as raw URLs, user IDs, or request IDs.

Naming guidance

• Keep service.name consistent across replicas of the same logical service.
• Put environment, version, region, and instance identity in separate resource attributes.
• Use low-cardinality operation names such as GET /orders/{id} instead of GET /orders/18427.
• Record request-specific values as span attributes only when they are safe and operationally useful.