Paulin Todev

I spoke with the Pyroscope team and they agree that this is a very valid request. The demand for this is likely to grow over time, so it is good...

Hello! Both the Alloy and the Pyroscope teams would welcome the addition of such a receiver component. However, it is not on our roadmap and I can't guarantee if (and...

Thank you, @marcsanmi! I'll close this issue because the new component has been released. If there are bug reports or feature requests, they could be raised by opening new issues.

So far I can think of two ways to do this. ### Option 1: Dynamic pipelines This option is being discussed in a dedicated proposal [PR](https://github.com/grafana/alloy/pull/1480). I'm not sure how...

Ideally we should come up with a solution which can also be reused for Loki components - #810.

I'll reopen this since [array.combine_maps function](https://github.com/grafana/alloy/pull/1826) doesn't entirely solve the issue. Hopefully the proposed [foreach block](https://github.com/grafana/alloy/pull/1480) will solve it.

It looks likely that we are going to go with the `foreach` option. I updated the PR to add some draft code that I've been working on. As a first...

@dependabot rebase

Hi, @PatMis16! Thank you for opening this issue. We could certainly add a new `otelcol.exporter.splunkhec` component. My only concerns with adding any new components is simply the maintenance cost. It...

Hi, @RalfWenzel 👋 This component was merged via #1885 and it'll be available in v1.6 as [otelcol.exporter.splunkhec](https://grafana.com/docs/alloy/next/reference/components/otelcol/otelcol.exporter.splunkhec/). Alloy v1.6 will be released on 2025-01-08. @PatMis16 Apologies, I never got around...