Repository navigation
feat(seer): Return triggering monitor on workflow runs - #130512
Merged
Merged
Conversation
Add a trigger field to the Seer workflow runs endpoint that identifies the monitor that started each run, read from the run's saved inputs. Runs not started by a monitor return null. Co-Authored-By: Claude <noreply@anthropic.com>
github-actions
Bot
added
the
Scope: Backend
Parse run extras and breached-metric inputs with their models instead of reading nested dict keys. Runs without a snapshot return null quietly; invalid data is logged. Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
Rename the trigger type to breached_metric and return the detector, event, occurrence, issue, project, environment, and observation time from the saved breach inputs. Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
aliu39
marked this pull request as ready for review
November 9, 2026 21:47
trevor-e
approved these changes
Nov 9, 2026
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 59a1a63. Configure here.
Co-Authored-By: Claude <noreply@anthropic.com>
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.
The Seer workflow runs list now says which metric breach started each run, so the automations UI can link a run back to its monitor, issue, and event.
Each run gets a
triggerfield. For runs started by a metric monitor, it hastype: "breached_metric"and the detector, event, occurrence, issue, project, environment, and breach time. Other runs returnnull. Thetypefield leaves room for other kinds of triggers later.No new storage is needed. Runs started by metric monitors already save these details with the run's inputs. Older runs without them return
null.A deleted monitor's ID stays on its runs, so the frontend needs to handle links to monitors that no longer exist. The frontend type change will follow in a separate PR.