Sebastian Poxhofer

No, shouldn't make any difference as these proxies return all available versions even the retracted ones. Regardless, the implementation will be easier when using proxies as we can download the...

Implementation proposal: - Wait for [OTEL MVC](https://github.com/renovatebot/renovate/pull/15731) in v33 - Add OTEL metrics implementation - Add [opentelemetry-prometheus-exporter](https://www.npmjs.com/package/@opentelemetry/exporter-prometheus) component and allow to enable it based on environment variables

OTEL is push based. True, the additional Prometheus exporter is only useful for long running instances.

Closing this issue as suggested https://github.com/renovatebot/renovate/issues/4051#issuecomment-1252208396. For further tools please open a separate feature requests.

@cartermp Are you working on this? I would really like to see a `SugaredTracer` with some additional convenience functions. If not, I would start to look into it myself.

Async workflows usually have multiple consumers with different use cases. The intention is to show async with OTEL in a common scenario and that both spans are added to the...

I have started working on this.

I have looked into this. I don't see how this could work at the moment, at least for `/api/v4/`. What we need is an option to deactivate the testing of...

What would be interesting is to integrate KSpan in the [k8clustereventreceiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/k8seventsreceiver) to allow it to export additionally traces instead of only logs. This would also reduce maintenance complexity as we...

I'm not against creating a CRD, far from it. What you are describing, is how I have imagined it. This way the user can consume the events outside of the...