Robert Pająk

By @jmacd in https://github.com/open-telemetry/opentelemetry-specification/issues/4256#issuecomment-2486236831: > In the Lightstep metrics SDK, we have added a [MeasurementProcessor API](https://github.com/lightstep/otel-launcher-go/blob/main/lightstep/sdk/metric/README.md#measurementprocessor) which has been discussed in the OpenTelemetry specification as far back as the OpenCensus...

> Hi there, I want to ask whether this is something ready to be implemented (e.g. the AttributesProcessor in View) , There is nothing like that in this moment. >...

Please sign the CLA.

Is there any prototype? @Blinkuu, are you prototyping it in Go somewhere?

> I could gladly use some help When I finish some things related to logs I can try prototyping it in Go.

I spend a few hours trying to prototype in OTel Go. Unfortunately, decided to abandon the effort as it seems to require substantial code changes.

We discussed this proposal during the last OTel Go SIG meeting ([notes](https://github.com/open-telemetry/opentelemetry-go/issues/6648#issuecomment-3060747994)). We have concerns about introducing the ability to drop or modify measurements: - **Narrow use case:** We could...

> This doesn't sound like how things are supposed to work (e.g., exporters aren't owned by readers since exporters are stateless) This is how it is supposed to work according...

For Go SDK it would be a problem only for stateful exporters. I think this change will be difficult to implement to have it out if the box. The problem...

> Exactly, this is my suggestion to implement a refcount in the exporter, to effectively delay the shutdown when all readers are shutdown Exporter is an interface. This would be...