Paschalis Tsilias

This change has been ported over in https://github.com/grafana/agent/pull/3942/, so closing this as completed 🙌

Hey there @Upanshu11. We're no longer actively tracking closed issues; I just happened to see this. If you think there's still new information, could you please open a new issue...

Good to hear, thanks!

Hey there! 👋 Yes, that sounds like an interesting idea! Would you like to take a shot at creating an Agent Flow component for it? We can provide guidance around...

@rafilkmp3 Apologies I totally missed your initial message. In case you're still interested, you can take some inspiration from grafana/agent#2604; implementing a new `mimir.alertmanager.kubernetes` component.

Good point about noisy components, we'll figure out a way to trim this down. A stream of logs would that is enabled on demand would be the best, but even...

That's weird as indeed, the readiness probe reuses the listenPort. https://github.com/grafana/alloy/blob/3201389252d2c011bee15ace0c9f4cdbcb978f9f/operations/helm/charts/alloy/templates/containers/_agent.yaml#L50-L56 Could it be related to [this change](https://github.com/grafana/alloy/commit/259e1bb074c1246f2c2eedb6a13e872eaad27fe1) last month for merging the agent and alloy keys, and it picking...

Here's a short reproduction on main (currently on https://github.com/grafana/agent/commit/2f4b5b37ac470fa5b0ebecb039495d8d397b711e). I'm running `go1.18 darwin/arm64` 1. Checkout and build the Agent. Run it with integrations-next enabled and the following config (basically `agent-local-config.yaml`...

To add some context around the upstream status of this issue; we've had support for recording Metadata as WAL records and storing them from the scrape loop for a while...

Hey @akselleirv, apologies for the belated response. What you're describing would _not_ be actually possible with Flow, until we have Operator components that can read the Prometheus CRDs. I suppose...