Bogdan Drutu
Bogdan Drutu
Please add changelog entry
@iblancasa I will do all the comments I asked you and did not do... In the followup
Needs a rebase.
I think we should start working on this, because we cannot delay until the stability.
This is good, but less than ideal. See https://github.com/open-telemetry/opentelemetry-collector/pull/11365 The best performant way is to actually construct the full `MeasurementOption` (result of `metric.WithAttributeSet(attribute.NewSet(attribute.String("exporter", exporter)))`) otherwise if I am not mistaken...
Please explain the motivation.
> I would expect that opentelemetry integration would be done via this- https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation > > and not via a hack in the actual library that breaks the driver for anyone...
You can achieve this by configuring the `without_type_suffix = true`, see also https://github.com/open-telemetry/opentelemetry-collector/issues/12458
Can I ask a different question. Is the nop exporter/processor really useful as a standalone component? Can I get some arguments why we need that?