feat(investigations): Add orchestration control API - #123086
Draft
arslnb wants to merge 2 commits into
Draft
Conversation
Create agentic investigation runs through the existing collection endpoint and expose durable orchestration state and idempotent command acceptance through private organization-scoped APIs.
github-actions
Bot
added
the
Scope: Backend
github-actions
Bot
added
the
Scope: Frontend
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
1 participant
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.
Adds the private Sentry control API for agentic investigations on top of #122972. Source-backed requests now reuse the existing collection endpoint: manual context and canonical metric-open-period references create the investigation, project links, and orchestration run atomically, while existing manual and template creation remain unchanged.
Existing list, detail, and candidate responses expose compact orchestration status. New organization-scoped routes return the durable projection and accept six strictly validated, idempotent commands under row locking. This slice intentionally stops at command persistence: it does not add Seer dispatch, event reduction, report materialization, frontend changes, or migrations.