Skip to content

Conversation

@cathteng
Copy link
Member

Resolves #103881

These metric alerts don't fire nor are they visible through the API

@cathteng cathteng requested a review from a team November 24, 2025 19:31
@cathteng cathteng requested a review from a team as a code owner November 24, 2025 19:31
@cathteng cathteng enabled auto-merge (squash) November 24, 2025 19:31
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Nov 24, 2025
@cathteng cathteng disabled auto-merge November 24, 2025 19:43
@cathteng cathteng enabled auto-merge (squash) November 24, 2025 19:44
organization=organization
).count()
alert_count = AlertRule.objects.fetch_for_organization(organization=organization)
# filter out alert rules without any projects
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

might want to leave a comment that this is an unusual buggy path that we don't expect to normally happen

@cathteng cathteng merged commit 4a72dcb into master Nov 24, 2025
67 checks passed
@cathteng cathteng deleted the cathy/alerts/filter-orphaned-metric-alerts branch November 24, 2025 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Organisation unable to create Metric Alert due to incorrect limitation

4 participants