search

grafana / alloy

OpenTelemetry Collector distribution with programmable pipelines
https://grafana.com/oss/alloy
Apache License 2.0
1.27k stars 172 forks source link

[mimir.rules.kubernetes] - Alert rules path naming #189

Open sergeyrudenko111 opened 5 months ago

sergeyrudenko111 commented 5 months ago

What's wrong?

Can't find a possibility to change alert rules path name, as example for something like - $cluster:$namespace:$alertRuleName. Current naming is - agent/$namespace/$alertRuleName/$id

Steps to reproduce

Regular alert rule creation by grafana-agent.

System information

No response

Software version

0.37.0

Configuration

mimir.rules.kubernetes "prometheus_rules" {
  address = "endpoint"
  sync_interval = "5m"
}

Logs

No response

rfratto commented 5 months ago

Hi there :wave:

On April 9, 2024, Grafana Labs announced Grafana Alloy, the spirital successor to Grafana Agent and the final form of Grafana Agent flow mode. As a result, Grafana Agent has been deprecated and will only be receiving bug and security fixes until its end-of-life around November 1, 2025.

To make things easier for maintainers, we're in the process of migrating all issues tagged variant/flow to the Grafana Alloy repository to have a single home for tracking issues. This issue is likely something we'll want to address in both Grafana Alloy and Grafana Agent, so just because it's being moved doesn't mean we won't address the issue in Grafana Agent :)

WhiteDiamondz commented 1 month ago

Would love that, I think by default it is pretty long and the id doesn't make it really user friendly when navigating the UI and searching for a specific alert namespace. Allowing to customise it for Loki as well would be a great enhancement !

I'm guessing this would be done in this file (? https://github.com/grafana/alloy/blob/main/internal/component/loki/rules/kubernetes/events.go#L201