Skip to content

Conversation

@iamrajjoshi
Copy link
Collaborator

Following up #95475

Once we build out the ability for the NOA to send Metric Issue Resolution notifications, we want to make sure we don't double notify and send an activity notification as well.

For slack, it is not powered by activity.send_notification rather a receiver on the Activity model, so I need to separate case it as well.

I also updated the check from group_category to type_id since the group_category is mainly for the FE and can change.

@iamrajjoshi iamrajjoshi self-assigned this Jul 14, 2025
@iamrajjoshi iamrajjoshi requested review from a team as code owners July 14, 2025 20:44
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jul 14, 2025
Copy link
Member

@GabeVillalobos GabeVillalobos left a comment

Choose a reason for hiding this comment

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

Changes seem reasonable

Comment on lines +160 to +163
metric_resolved_notification = (
activity.type == ActivityType.SET_RESOLVED.value
and activity.group.issue_type.type_id == MetricIssue.type_id
)
Copy link
Member

Choose a reason for hiding this comment

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

Future improvement -> Is this something that should be moved to the activity class, or some shared utils file for classifying metric notifications?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

ideally we don't do this logic in the future imo

@iamrajjoshi iamrajjoshi merged commit 3ed84cf into master Jul 15, 2025
65 checks passed
@iamrajjoshi iamrajjoshi deleted the raj/aci/dont-send-slack-notifs-for-metric-alert branch July 15, 2025 13:42
andrewshie-sentry pushed a commit that referenced this pull request Jul 21, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Jul 31, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants