Alert with set environment no closing integration issues when the Sentry issue is resolved.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
- Create a metric monitor in an environment (used dev for testing)
- Create an alert to open an issue in an integration (used OpsGenie)
- Configure the alert to only trigger in the same environment as the monitor
- Connect the monitor to the alert.
- Trigger the metric monitor
- Resolve the metric monitor
Expected Result
The alert creates a new issue in the integration when the alert is triggered and resolves the issue when the issue in Sentry is resolved (metric monitor is back to baseline).
Actual Result
When selecting an environment in the alert settings, the issue in OpsGenie was not resolved automatically by Sentry.
Only when selecting "All Environments", the issue in OpsGenie was correctly closed.
Monitor link
Alert link
Looking at the logs in Sentry, the action to close the issue in OpsGenie is never sent, thus this is not an issue with OpsGenie but with the alert not sending the signal to the integration.
Product Area
Alerts
Link
No response
DSN
No response
Version
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the metric monitor and environment-filtered alert flow using the supplied monitor and alert links, then inspect the alert logs for the missing OpsGenie close signal. Done means resolving the Sentry issue after the monitor returns to baseline emits the integration close action for the selected environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100