You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was observed that some detectors can provide global IDs while others can only provide local IDs within a particular context. For example, the k8s node detector can only provide a unique k8s.node.uid within a particular cluster.
Do we need to require identifying attributes to be always globally unique? Can we instead use a composition of entities attached to a particular resource, where each entity is only global within the context of another "parent" entity (e.g., k8s node -> k8s cluster)? That way, it'll be much easier to combine detectors responsible for different entity types.
The text was updated successfully, but these errors were encountered:
dmitryax
changed the title
Do we always require identyfing attributes to be globally unique?
[entities] Do we always require identyfing attributes to be globally unique?
Oct 10, 2024
dmitryax
changed the title
[entities] Do we always require identyfing attributes to be globally unique?
[entities] Do we always require identifying attributes to be globally unique?
Oct 10, 2024
This was discussed during the Entities SIG meeting on Oct 10. The tentative agreement is that entities will only have local IDs. Global identification will be achieved by combining different parent-child entities. This is the direction we are going to continue prototyping
Similar to #4253, this question is the result of prototyping of entity detection in the collector open-telemetry/opentelemetry-collector-contrib#35538.
It was observed that some detectors can provide global IDs while others can only provide local IDs within a particular context. For example, the k8s node detector can only provide a unique
k8s.node.uid
within a particular cluster.Do we need to require identifying attributes to be always globally unique? Can we instead use a composition of entities attached to a particular resource, where each entity is only global within the context of another "parent" entity (e.g., k8s node -> k8s cluster)? That way, it'll be much easier to combine detectors responsible for different entity types.
The text was updated successfully, but these errors were encountered: