- Resource attributes that come from the server are prefixed with `resource.`. Since we have all attributes available, we need a way to tell which ones belong to the resource and which belong to the span. Tempo is a bit odd: if you request `select(resource.serviceAttributeName)`, it will appear on the span as `serviceAttributeName`, but because you requested it in the select you can trace it back to a resource attribute. In production, however, we receive all values without requesting them, so the `resource.` prefix is necessary to identify which attributes are resource attributes.
0 commit comments