Idea: Remove the grafanaAgent from the helm chart

[whg517]

Do we have any plans to remove the grafanaagent from the helm chart?

In the early days, I used the alloy project to customize the monitoring of Loki, Mimir, Temp, and Alloy components. Now that the hlem chart is being managed within the corresponding project in the community, we have also adopted the new version for deployment. I have discovered that the Loki project can directly integrate with Prometheus-operator for metric collection through configuration.

In the Helm chart of the mimir project, although a similar implementation was used, there was a strong reliance on the configuration switch of the grafanaagent. That is, if metaMonitoring.grafanaAgent.enable is not enabled, the ServiceMonitor resource will not be installed. This is extremely inconvenient for the integration of the scheme.

I noticed that the content related to grafanaAgent has been marked as deprecated quite some time ago. I would like to know if there is a clear plan within the community to remove it and provide an integration solution that is the same as Loki's chart.

[narqo]

Starting Helm chart 6.0 the documentation on monitoring Mimir cluster in production says

The Grafana Mimir Helm chart contains built-in configurations for meta-monitoring that use the Grafana Agent, which is now deprecated. We no longer recommend using this approach. Instead we recommend an approach that is based on Kubernetes Monitoring Helm chart.

Kubernetes Monitoring comes with the built-in Mimir integration, that collects metrics, logs, and traces from Grafana Mimir. It configures Grafana Alloy to handle all scraping and log collection automatically.

We will possibly remove the dependency from deprecated Grafana Agent in the next major release. As of today, there aren't exact plans for when this will be.