Alex Boten

The different configuration files is also confusing..

As discussed in 17-Apr-2024 - The same command could just be a symlink to ensure the change isn't breaking backwards compatibility

Opened a separate issue for configuration consistency: https://github.com/open-telemetry/opentelemetry-collector-releases/issues/530

Pinging code owners on this: @boostchicken @gouthamve @jpkrohling @MovieStoreGuy

Thanks for the feedback! I'll spend some time and try to repro, its possible the github api has changed since i'd originally written the code. I'll see if i can...

There's an otep that discusses additional details around monitoring a telemetry pipeline https://github.com/open-telemetry/oteps/pull/259, might be worth taking a look there as well

updated the test in https://github.com/open-telemetry/opentelemetry-collector/pull/10519, @mx-psi PTAL

@mx-psi as it's a change in the underlying library, we don't usually document those

I agree that it makes sense to keep the returned error with Shutdown. Unless others feel strongly about this, I suggest we close this issue

Came across this bug as I was making the change https://github.com/open-telemetry/opentelemetry-collector/pull/10233. The measurement for this metric doesn't add the attributes that other metrics do