getsentry / getsentry/self-hosted
Alert rule for "New Issue Created" is not triggered immediately.
- Dominant language
- Shell
- Stars
- 9.6k
- Forks
- 2k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 12
Description
### Environment
self-hosted (https://develop.sentry.dev/self-hosted/)
### Steps to Reproduce
Hi, I have Sentry deployed in k8s using https://github.com/sentry-kubernetes/charts, and for an alert to be sent when a new Issue created I need to create an Issue (1 event in it) and send another event to any Issue - only then will the alert be sent.
I have a custom WebHook Integration with subscribe to "created":
Also i have alert rule:
And their behavior is equally incorrect.
Previously i have a version 25.3.0, upgrading to 25.5.1 not solve the problem.
### Expected Result
An alert is sent immediately after an Issue is created (1 event).
### Actual Result
An alert is sent only after an event has been sent for any Issue.
### Product Area
Alerts
### Link
_No response_
### DSN
_No response_
### Version
25.5.1
Contributor guide
Research direction
Reproduce the behavior in self-hosted Sentry 25.5.1 using the Kubernetes deployment and the reported "created" webhook subscription and alert rule. Trace the alert and webhook processing triggered by the first issue event, then verify that both notifications are sent immediately without requiring a later event on another issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100