Alex Boten

> A contrib test [failed](https://github.com/open-telemetry/opentelemetry-collector/actions/runs/10743816191/job/29799409203?pr=10910#step:4:707), but I think it expected with this change: > > ``` > === Failed > === FAIL: . TestFilterMetricProcessorTelemetry (0.00s) > make[3]: *** [../../Makefile.Common:128: test]...

This needed an update of `PtrTo` -> `PointerTo`. Addressed the following warning as well: ``` WARN The linter 'exportloopref' is deprecated (since v1.60.2) due to: Since Go1.22 (loopvar) this linter...

There's still a linter failure, will address it in a separate issue/PR

> However, I don't see that warning message in my collector startup logs. The warning will now show up by default with the featuregate moving to stable in https://github.com/open-telemetry/opentelemetry-collector/pull/11091 >...

I tested this via the current version of the collector with the config: ``` service: telemetry: metrics: address: "" readers: - periodic: exporter: otlp: protocol: http/protobuf endpoint: https://api.honeycomb.io:443 headers: "x-honeycomb-team":...

Note that the export of the metrics via OTLP happened over two different batches, not sure if that's important to your tests @pirgeo

@pirgeo was able to reproduce a similar behaviour as what you described by programmatically disabling the prometheus exporter configured via `metrics::address`, will do more testing

submitted a fix for the bug in https://github.com/open-telemetry/opentelemetry-collector/pull/11093

> I am opening this issue to discuss possible solutions. Here are a few I came up with > >Setting the address to `null` explicitly should disable the Prom exporter...

It looks like the source of these metrics are from the googlecloud exporter? Maybe @dashpole knows more here