You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is similar to #47424. When an alert is created in a multi-org environment, outside of a dashboard or panel, by going through Alerting -> New Alert rule, the generated alert URL will not have the orgId parameter attached to it. This causes an "alert not found" within multi-org environments.
This was fixed for dashboard and panel URLs but not alerts created outside of those context in #57123. The logic should extend to creating alerts manually.
What you expected to happen:
Alerts created via Alerts -> New alert rule should include the appropriate source URL with the orgId parameter in a multi-org environment.
How to reproduce it (as minimally and precisely as possible):
Be in a multi-org environment
Create an alert via Alerts -> New alert rule
Fire the alert
Notice that the Source URL in the alert notification does not contain the correct orgId and will not go to the appropriate organization/alert.
Anything else we need to know?:
It looks like all the alerting logic was moved to the repo: https://github.com/grafana/alerting in main and v9.4.x, but it's still here in v9.3.x.
I think the change should be simple enough and I'm fine with cutting a PR for this, but I wasn't sure where the change should go. If it's in v9.4.x, and I make a PR to https://github.com/grafana/alerting, we'd have to also bump the go.mod here, correct?
Environment:
Grafana version: 9.3.8
Data source type & version: Prometheus
OS Grafana is installed on: Linux
User OS & Browser: Firefox
Grafana plugins: N/A
Thanks!
The text was updated successfully, but these errors were encountered:
Yes, the grafana/alerting repo is the right place for this fix. We bump its version periodically, but we'd also happily accept an external PR to bump its version once your original PR goes in.
Unfortunately, both fixes will not be in 10.0.0 as the PR that updated alerting module was merged too late. The fixes will be in the next patch release.
What happened:
This is similar to #47424. When an alert is created in a multi-org environment, outside of a dashboard or panel, by going through Alerting -> New Alert rule, the generated alert URL will not have the
orgId
parameter attached to it. This causes an "alert not found" within multi-org environments.This was fixed for dashboard and panel URLs but not alerts created outside of those context in #57123. The logic should extend to creating alerts manually.
What you expected to happen:
Alerts created via Alerts -> New alert rule should include the appropriate source URL with the
orgId
parameter in a multi-org environment.How to reproduce it (as minimally and precisely as possible):
Source
URL in the alert notification does not contain the correctorgId
and will not go to the appropriate organization/alert.Anything else we need to know?:
It looks like all the alerting logic was moved to the repo: https://github.com/grafana/alerting in
main
andv9.4.x
, but it's still here inv9.3.x
.v.9.3.x
in this repo:grafana/pkg/services/ngalert/notifier/channels/template_data.go
Lines 107 to 109 in b34f977
I think the change should be simple enough and I'm fine with cutting a PR for this, but I wasn't sure where the change should go. If it's in v9.4.x, and I make a PR to https://github.com/grafana/alerting, we'd have to also bump the
go.mod
here, correct?Environment:
Thanks!
The text was updated successfully, but these errors were encountered: