f905ac5246
# What this PR does - Add a new column, `grafana_incident_id`, to the `AlertGroup` model. For now this is really just needed to determine if the Alert Group was created, via a Direct Page, that originated from Grafana Incident. - I understand that these IDs may be cluster specific. For now we will not need to make OnCall backend -> Incident API calls. Should we need to start doing this we will likely need to start syncing the Incident plugin's provisioned API url into the `organization` in OnCall, such that we make the API call to the right Incident backend. - Add two new optional request body parameters to `POST /direct_paging`, `source_url` and `grafana_incident_id` - `source_url` - will easily allow Grafana Incident to specify the URL to the Incident and have this populate the "Source" button - `grafana_incident_id` - Grafana Incident can specify this such that we have a link back to Incident (+ we know that the Alert Group was generated from Incident) - Hide the "Declare Incident" button in the UI if the Alert Group was generated from Grafana Incident ## Checklist - [ ] Unit, integration, and e2e (if applicable) tests updated - [ ] Documentation added (or `pr:no public docs` PR label added if not required) - [ ] `CHANGELOG.md` updated (or `pr:no changelog` PR label added if not required) |
||
|---|---|---|
| .. | ||
| escalation_snapshot | ||
| grafana_alerting_sync_manager | ||
| incident_appearance | ||
| incident_log_builder | ||
| migrations | ||
| models | ||
| tasks | ||
| tests | ||
| __init__.py | ||
| constants.py | ||
| integration_options_mixin.py | ||
| paging.py | ||
| representative.py | ||
| signals.py | ||
| utils.py | ||