Repository navigation
feat(automations): Run Slack channel automations on named bot posts - #2197
Open
sentry-junior[bot] wants to merge 1 commit into
Open
sentry-junior[bot] wants to merge 1 commit into
sentry-junior[bot] wants to merge 1 commit into
Conversation
A Slack channel-message automation dropped every bot post, so an automation meant to triage Sentry alert posts could never run. Bot posts now publish with postedByBot, and they run only automations whose match names the bot in userId. Other automations in the channel still ignore bot posts, so a noisy bot cannot use up their run limits. Co-Authored-By: Michael Warkentin <michael@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Slack channel-message automations dropped every bot post at ingress. So an automation built to triage Sentry alert posts in a channel could never run, because the alerts come from the Sentry bot.
Now bot posts (other than Slackbot) publish a
message.postedevent markedpostedByBot. Theslack/channelresource type adds auserIdmatch field. A bot post runs only automations whosematch.userIdnames that bot. Automations without auserIdmatch still ignore bot posts, so a noisy bot cannot use up their hourly run limits. Junior's own posts are still dropped earlier by theisMecheck, so this cannot loop.Example trigger:
match: { userId: "U012F5JFM1A" }for Sentry alert posts.via michael.
--
View Junior Session [Sentry]