Paulin Todev

Thank you! Could you please comment on the [other issue](https://github.com/grafana/alloy/issues/224)? I'm not able to assign it to you otherwise. There's a restriction in the GitHub settings, so I can't see...

I'm personally happy for us to use bottles. I'm just not sure how to test this. It'd be nice to have CI tests as well. I suppose we'd have to...

If OTel has enabled it by default, then it would be ok for us to incorporate it. The dev team is a bit busy right now so I'll let the...

There isn't an easy way to find them. Unlike cmd args, env vars could be referenced anywhere in the code, including in libraries which we import. This is what makes...

Hi, @wildum - would you like to close this PR?

I had a look at this today. Apparently Prometheus has a feature called "unchecked collectors". It is mentioned in their [docs](https://pkg.go.dev/github.com/prometheus/[email protected]/prometheus): > Alternatively, you could return no Desc at all,...

I tried using normal collectors such as `prometheus.Counter`, but it wasn't possible. Apparently, Prometheus registries don't allow registering the same metric multiple times if it has different const labels[^1]. I...

The `cri` and `docker` stages do configure an output source. For `docker`, `source` is `output ` whereas for `cri`, `source` is `countent`. This debug line gets printed not when `source`...

@PieterScheffers If everything is working normally, then you're not supposed to see these log lines even if debug logging is enabled. I suppose in your case the `cri` stage isn't...

Hi @AndreZiviani, thank you for raising an issue! Aer you referring to Pprof profiles? Is there a reason why `pyroscope.scrape` would not be sufficient for the purposes listed above?