Skip to content

feat(investigations): Apply update_detector action requests - #128724

Open
wedamija wants to merge 9 commits into
danf/inv-fu-17-update-detector-applyfrom
danf/inv-fu-25-apply
Open

wedamija wants to merge 9 commits into
danf/inv-fu-17-update-detector-applyfrom
danf/inv-fu-25-apply

Conversation

@wedamija

Copy link
Copy Markdown
Member

Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click.

This adds an Apply button to a suggested monitor change. When the card shows, it asks the backend with a dry run whether the change would apply, and says why when it can't, so the user only clicks a change that will save.

Depends on #128681 and #128723

@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Oct 23, 2026
@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Story previews

Preview the stories changed in this PR on the Vercel deployment:

Preview deployment: https://sentry-cnemilq73.sentry.dev

@wedamija
wedamija changed the base branch from master to danf/inv-fu-17-update-detector-apply October 23, 2026 23:28
@wedamija
wedamija marked this pull request as ready for review October 23, 2026 23:28
@wedamija
wedamija requested a review from a team as a code owner October 23, 2026 23:28
@wedamija
wedamija force-pushed the danf/inv-fu-17-update-detector-apply branch from 96b9f20 to 82a3121 Compare October 23, 2026 23:28
@wedamija
wedamija force-pushed the danf/inv-fu-25-apply branch from 5ae36d2 to 50d1502 Compare October 23, 2026 23:28
@wedamija
wedamija force-pushed the danf/inv-fu-17-update-detector-apply branch from 82a3121 to b40ebfd Compare October 24, 2026 01:10
@wedamija
wedamija requested review from a team as code owners October 24, 2026 01:10
@wedamija
wedamija force-pushed the danf/inv-fu-25-apply branch from 50d1502 to 675c6e9 Compare October 24, 2026 01:13
wedamija added a commit that referenced this pull request Oct 24, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click.

This keeps an action request on the card after it's applied or fails, showing who applied it and what changed on the monitor, or why the change didn't save.

Depends on #128724

@cursor cursor Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Stale Bugbot comment from a previous run.

@wedamija
wedamija force-pushed the danf/inv-fu-17-update-detector-apply branch from b40ebfd to 0c3a92b Compare October 24, 2026 01:30
@wedamija
wedamija force-pushed the danf/inv-fu-25-apply branch from 675c6e9 to 884eb5c Compare October 24, 2026 01:30
wedamija added a commit that referenced this pull request Oct 24, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click.

This keeps an action request on the card after it's applied or fails, showing who applied it and what changed on the monitor, or why the change didn't save.

Depends on #128724
@wedamija
wedamija force-pushed the danf/inv-fu-17-update-detector-apply branch from 0c3a92b to 54109e5 Compare October 24, 2026 03:49
@wedamija
wedamija force-pushed the danf/inv-fu-25-apply branch from 884eb5c to 94355e6 Compare October 24, 2026 03:51
wedamija added a commit that referenced this pull request Oct 24, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click.

This keeps an action request on the card after it's applied, showing who applied it and what changed on the monitor. When the backend rejects a change, the card says why and leaves Apply available.

Depends on #128724
@github-actions

github-actions Bot commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor

📊 Type Coverage Diff

Metric Before After Delta
Coverage 95.78% 95.79% 🟢 +0.01%
Typed 141,473 141,573 🟢 +100
Untyped 6,227 6,228 🔴 +1
🔍 1 new type safety issue introduced

Type assertions (as) (1 new)

File Line Detail
static/app/views/investigations/actionRequests/actionKinds.tsx 47 as K — action.kind as K

This is informational only and does not block the PR.

@cursor cursor Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Stale Bugbot comment from a previous run.

wedamija added a commit that referenced this pull request Oct 24, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click.

This keeps an action request on the card after it's applied, showing who applied it and what changed on the monitor. When the backend rejects a change, the card says why and leaves Apply available.

Depends on #128724
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click.

This adds an Apply button to a suggested monitor change. When the card shows, it asks the backend with a dry run whether the change would apply, and says why when it can't, so the user only clicks a change that will save.

Depends on #128681 and #128723
The button stays disabled while the dry run runs and keeps its last answer through a refetch. Only a rejection with a code blocks it, the reason uses the code's copy, and it's linked for screen readers. The check reruns when Seer changes the action.
…action

The dry run kept its last answer as placeholder data, so the button stayed enabled for a change that hadn't been checked. A refetch of the same check keeps its data anyway, so the placeholder isn't needed.
Move update_detector's apply button, details and copy into a per-kind
object, and say per kind whether the UI checks a change before applying
it. Refetch only what an apply changed, type the request error with the
apply error schema, and drop the shared stale copy no kind reaches.
A disabled query still reports pending, so a kind without a pre-apply check kept a busy, disabled button.
Only stale, already_applied and withdrawn refreshed it, so a superseded or no longer permitted request kept an enabled button until a reload.
…er hidden one

A superseded primary with a higher id hid the live suggestion.
@wedamija
wedamija force-pushed the danf/inv-fu-25-apply branch from 18468b3 to d954e3a Compare October 24, 2026 06:13
wedamija added a commit that referenced this pull request Oct 24, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click.

This keeps an action request on the card after it's applied, showing who applied it and what changed on the monitor. When the backend rejects a change, the card says why and leaves Apply available.

Depends on #128724

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit d954e3a. Configure here.

Comment thread static/app/views/investigations/actionRequests/nextStepCard.tsx Outdated
…xt step

Skipping applied primaries made a completed next step look missing, so the page refetched and showed the loading placeholder.
wedamija added a commit that referenced this pull request Oct 24, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click.

This keeps an action request on the card after it's applied, showing who applied it and what changed on the monitor. When the backend rejects a change, the card says why and leaves Apply available.

Depends on #128724

This branch was successfully deployed

1 active deployment
Preview — 611fe2ec Deployed Oct 24, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant