When investigating #2775, the TC decided to look into expanding the notion of Resource
to include Entity
.
During this discussion, we identified a lot of hard, challenging problems OpenTelemetry must tackle going forward, including:
- Telemetry Identity evolving as "scope" increases. E.g. a Jaeger instance running in a single k8s cluster may not need to know the identity of the k8s cluster, as there's only one. However, a datastore spanning mulitple k8s clusters WILL need this information.
- A simple "Service" model for OpenTelemetry SDKs (e.g. requiring
service.name
attribute) works in the short run, but beings to struggle in large distributed systems. - Defining a consistent guideline on what resource / entity means in practice, how to choose one and what our Entity <-> Signal modelling needs to look like in the long run.