Paulin Todev

This issue should now be resolved because Alloy is now using a new OTel version with the bugfix mentioned above.

A Flow component for this has been requested by @cyrille-leclerc. IMO we should consider this issue (#454) to only have the Flow component in scope, and we should only consider...

Although the Agent hasn't ported the Collector's [resource processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/resourceprocessor/README.md), it did port over the [transform processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/transformprocessor/README.md) in the form of [otelcol.processor.transform](https://grafana.com/docs/agent/latest/flow/reference/components/otelcol.processor.transform/). As [this](https://github.com/grafana/agent/issues/2910#issuecomment-1594423405) comment says, the transform processor is set...

I'm closing this issue because [otelcol.processor.transform](https://grafana.com/docs/alloy/latest/reference/components/otelcol.processor.transform/) is considered "stable" in Alloy.

Hi, @etiennep! Your point about the resource processor having the `from_context` is a valid one. I'll check if there are plans to support it in the transform processor. If there...

@etiennep I opened a new [issue](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/33288) in the upstream Collector repo for the transform processor to have an equivalent to the resource processor's `from_context` config argument. The transform processor's maintainers...

Hi @captncraig, would you like to merge the PR? I rebased it for you :)

Hi, @psychomantys! I opened a [PR](https://github.com/grafana/alloy/pull/1326) for Alloy to support this feature. The Alloy PR is based on yours, and credits will go to you in the Alloy changelog. Thank...

> We noticed that the agent adds a label "instance" corresponding by default to the host where the agent runs to the targets. Is this correct? According to [this doc...

I think the bug in the clustering can be fixed if SNMP exporter's `InstanceKey` [function](https://github.com/grafana/agent/blob/196ea058806a42c8b24723fde82e8dcfc5f3e919/internal/static/integrations/snmp_exporter/snmp_exporter.go#L58-L61) is changed to return the addresses of the targets which are actually being scraped, similarly...