Edward Park

@pintohutch for me, the most helpful info from those page routes is the status of the deployed rules -- we'd want to make sure that rules are correctly registered at...

yeah we're hitting the same exact behavior - we're using the `loki-distributed` helm chart for our loki components as well 200s at the ruler level, but 404s at the gateway...

one additional observation - clicking the button doesn't change the view state, so the user doesn't know whether or not grafana registered the click (leading to some spam clicking)

checking on the failed lint job, sec

@r3code our alerting config looks something like this: ```yaml alerting: name: SLOBurnRateTooHigh labels: custom_slack_channel: "slo-multiwindow-burn-rate-alerts" annotations: description: '`{{$value | humanizePercentage}}` error rate for `{{$labels.sloth_id}}`' dashboard: "https://grafana.company.org?service={{$labels.sloth_service}}&var-slo={{$labels.sloth_slo}}" page_alert: labels: severity: warning...

ahh interesting. yeah im avoiding jsonnet as much as possible, but maybe that's the only way to customize further

oh @jamiezieziula - we can `kubectl logs` by deployment name, eg. ``` kubectl logs deployment/shoveler | grep something-interesting ```

im not the OP, but i can share a use case. basically, if you're using prometheus (and GMP to house the collections and handle collecting/rule evaluations), you probably like the...

no doubt @pintohutch ! one possible short-term way to support this ask is possibly to expose the `/api/v1/rules` [API](https://prometheus.io/docs/prometheus/latest/querying/api/#rules) from one of the managed GMP components (rule-evaluator seems to make...

to share our experience - we're on Google for GKE and group-based RBAC in the cluster. these help us use flux safely across the team and not have to managed...