Repository navigation
feat(seer): Add investigation entrypoint and operator scaffolding - #126900
Merged
alexsohn1126 merged 1 commit intoOct 14, 2026
Merged
Conversation
Contributor
Sentry Snapshot Testing
|
joseph-sentry
approved these changes
Oct 9, 2026
| slack_user_id: NotRequired[str] | ||
|
|
||
|
|
||
| class SlackInvestigationCachePayload(TypedDict): |
Contributor
There was a problem hiding this comment.
is it a limitation of the entrypoint + operator pattern that these payloads are stored in redis with the 24 hour expiry or is the storage medium configurable?
Member
Author
There was a problem hiding this comment.
Storage medium is def configurable, but thought I'd follow the existing pattern until this project ends, I think there is a benefit to be had by moving these to a table perhaps, needs more thinking though
Comment on lines
+87
to
+95
| organization_id: int | ||
| integration_id: int | ||
| channel_id: str | ||
| thread_ts: str | ||
| alert_message_ts: str | ||
| status_message_ts: str | None | ||
| slack_user_id: str | ||
| last_sent_state: str | None | ||
| final_sent: bool |
Contributor
There was a problem hiding this comment.
could we add comments here describing the ambiguous fields? not sure what alert_message, statuse_message, last_sent_state, final_sent are? are these properties of Slack or Investigations?
alexsohn1126
force-pushed
the
alexsohn/cw-2134-investigation-entrypoint-scaffold
branch
from
October 13, 2026 18:57
844957d to
4c19333
Compare
Base automatically changed from
alexsohn/cw-2134-implement-slack-integration-for-investigations
to
master
October 14, 2026 14:18
alexsohn1126
force-pushed
the
alexsohn/cw-2134-investigation-entrypoint-scaffold
branch
from
October 14, 2026 14:18
4c19333 to
2aaade0
Compare
Add the SeerInvestigationEntrypoint protocol, an investigation entrypoint registry, SeerInvestigationOperator and a registered SlackInvestigationEntrypoint. All methods are no-ops for now, and nothing calls them yet. The real logic and the Slack click handler come in a follow-up. Refs CW-2134
alexsohn1126
force-pushed
the
alexsohn/cw-2134-investigation-entrypoint-scaffold
branch
from
October 14, 2026 15:51
2aaade0 to
5637639
Compare
alexsohn1126
deleted the
alexsohn/cw-2134-investigation-entrypoint-scaffold
branch
October 14, 2026 16:51
3 tasks done
alexsohn1126
added a commit
that referenced
this pull request
Oct 16, 2026
) Clicking the "Investigate with Seer" button on a Slack metric alert now starts a Seer investigation for that alert -- when the org has both the investigations flag and the Slack investigations flag turned on. #126723 added the button, and this fills in the empty pieces from #126900. When someone clicks, we first check that they've linked their Slack account to Sentry and that they're a member of the org. If they haven't linked, they get the usual prompt to link. If they aren't a member, the flags are off, or the org doesn't allow open membership (same rule as the investigations page), they get a message only they can see saying why. The alert and open period from the button are looked up within the org, so a click can't reach another org's alert. If an investigation already exists for that open period, they just get a link to it. When a new investigation starts, the button on the alert turns into an "Open investigation" link, and we post "`@someone` started a Seer investigation for this alert." in the alert's thread. That thread message, and the private message someone gets if Seer can't start the investigation, are built with notification platform templates like our other Seer messages. We still post them ourselves, since the platform can't post in a thread. We keep the channel and thread in the cache for 24 hours so later updates know where to post. The started message is a one-time announcement and never gets edited. Live status comes in a follow-up, as a separate message in the thread that's posted once the investigation makes its first real progress. Refs CW-2134 Completes CW-2136
RudraPatel2003
pushed a commit
that referenced
this pull request
Oct 19, 2026
) Clicking the "Investigate with Seer" button on a Slack metric alert now starts a Seer investigation for that alert -- when the org has both the investigations flag and the Slack investigations flag turned on. #126723 added the button, and this fills in the empty pieces from #126900. When someone clicks, we first check that they've linked their Slack account to Sentry and that they're a member of the org. If they haven't linked, they get the usual prompt to link. If they aren't a member, the flags are off, or the org doesn't allow open membership (same rule as the investigations page), they get a message only they can see saying why. The alert and open period from the button are looked up within the org, so a click can't reach another org's alert. If an investigation already exists for that open period, they just get a link to it. When a new investigation starts, the button on the alert turns into an "Open investigation" link, and we post "`@someone` started a Seer investigation for this alert." in the alert's thread. That thread message, and the private message someone gets if Seer can't start the investigation, are built with notification platform templates like our other Seer messages. We still post them ourselves, since the platform can't post in a thread. We keep the channel and thread in the cache for 24 hours so later updates know where to post. The started message is a one-time announcement and never gets edited. Live status comes in a follow-up, as a separate message in the thread that's posted once the investigation makes its first real progress. Refs CW-2134 Completes CW-2136
2 tasks done
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.
Sets up the pieces that let Seer start investigations from outside Sentry, starting with Slack. This PR only adds the shape; every method is a no-op and nothing calls them yet. The real logic and the Slack click handler come in #126751.
SeerInvestigationEntrypointprotocol andinvestigation_entrypoint_registry, following the existing autofix and agent entrypoints.SeerInvestigationOperatorwithhas_accessandtrigger_investigation.has_accessreturnsFalsefor now.SlackInvestigationEntrypoint, registered for Slack, and itsSlackInvestigationCachePayload.Refs CW-2134 CW-2136