Juha Tiensyrjä

Linking a couple of similar sounding issues here: * https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/30697 * https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/30835

Based on comments in #30697 I could reproduce this: 1. Set up the loadbalancing exporter with K8s resolver with two target pods. 2. Restart one of the target pods. 3....

> From the collector config, it doesn't look like you are actually using the prometheus receiver or prometheus exporter in a pipeline? No, I'm not. This can be reproduced easily...

Trying to gather my thoughts a bit here, so please forgive me if you find this messy. 1. Loadbalancing exporter starts and registers a metric `otelcol_exporter_queue_size{exporter="loadbalancing",service_instance_id="8b8c3359-8b34-488b-9f22-8cfa8081db97",service_name="otelcol-contrib",service_version="0.92.0"}`. * What registers this...

> @juissi-t, would you be able to test the repro with the current commits from this repository in your environment ? I synced the recent commits from Otel collector Git...

I tried to use the workaround today with the following results: 1. When using `nginx.ingress.kubernetes.io/auth-keepalive: "20"` annotation in an ingress, the auth request is not part of the full request...