Open jsuereth opened 3 weeks ago
We need the ability to understand if two observers are discussing the same entity. Should the entity have the same ID or should this situation be detectable?
We need some interaction between enttity, resource + ENV variable that doesn't break OTEL operator users (and others leveraging ENV variables).
Should we prevent duplicate entities from being emitted across all possible telemetry sources? Should we have an automatic way for the collector, e.g. to unify duplicate sources of entities and only emit one definitive signal?
Today during the otel-entities WG, we discussed values we'd use in rubrics to evaluate future OTEPs/Designs on entities. These are a set of principles we'd like to uphold, but can be flexible on. Designs to move forward with entities should list these conditions in pros/cons (at a minimum).
I'm opening this issue to record decsions and a follow on comment to add un-addressed items we need to decide upon.
Core Principles
kubectl get pods <name>
for a k8s pod.For an SDK - ALL telemetry should be associated with the same set of entities (resource labels).
These are some principles we agreed are important and will evaluate in our rubric on design choices.