Josh Suereth

So if you wanted to use a poor-man's substitute for now, `weaver` already (somewhat by accident of trying to make generic features) supports uniqueness requirements for `name` on group, and...

Adding @dmitryax document detailing some of our core issues here and thoughts on resolution: https://docs.google.com/document/d/1eAyPiQkbu9LvcmriUDCYkkGY_A3pT1m2FFg_w8s8uEc/edit?tab=t.0#heading=h.1nkx5p1ewcuv

We have added EntityRef to resource in OTLP. marking these as complete (we did the actions listed, just forgot to check them off)

Sadly I only had a few minutes to update this bug with some use cases, but here's the first two: ## Provide OTLP endpoints based on runtime environment. Ideally a...

A bit late: > > When running in production: the OTEL Operator providing knowledge to SDKs of exposed endpoints instead of requiring manual configuration of those endpoints. > I think...

I think I like option 3 the best, but could we include the attribute descriptions in the original table? Like @joaopgrassi I'm worried if folks need to jump up/down a...

@Cunei - Ping me when you start work this week. I think maybe we want to consolidate the dbuild git/svn branching code with Sbt's. IIRC - You had a bunch...

## Issue 1 - Multi observers We need the ability to understand if two observers are discussing the same entity. Should the entity have the same ID *or* should this...

## Issue 2 - ENV variable for resources We need some interaction between enttity, resource + ENV variable that doesn't break OTEL operator users (and others leveraging ENV variables).

## Issue 3 - Duplicate entity reporting Should we prevent duplicate entities from being emitted across all possible telemetry sources? Should we have an automatic way for the collector, e.g....