Yogeshwar Singh

I think we can close this issue because [scale out or in etcd clusters](https://kubernetes.io/docs/tasks/administer-cluster/configure-upgrade-etcd/#:~:text=A%20general%20rule%20is%20not%20to%20scale%20out%20or%20in%20etcd%20clusters.%20Do%20not%20configure%20any%20auto%20scaling%20groups%20for%20etcd%20clusters.%20It%20is%20highly%20recommended%20to%20always%20run%20a%20static%20five%2Dmember%20etcd%20cluster%20for%20production%20Kubernetes%20clusters%20at%20any%20officially%20supported%20scale.) is anyways not recommended and it is working perfectly fine otherwise in my case as well.

Hi @richburroughs , could you please assign this to me?

Is there any progress on this or is there any way I can help?

@fpetkovski are you seeing increase in persistent volume utilization as well for this particular receiver instance/pod?

I was also facing the same issue when ingesting metrics using OTel collector `prometheusremotewrite` exporter. The culprit seems to be the `target_info` metrics which are enabled by default. Sometime these...

The best way I know you can debug this is by changing the log level of the receiver from `info` to `debug`. Then you should be able to see what...