Skip to content

Add metric alert context to Seer issue details RPC#115332

Draft
JoshFerge wants to merge 2 commits into
masterfrom
jferg-codex/explorer-metric-alert-context-rpc
Draft

Add metric alert context to Seer issue details RPC#115332
JoshFerge wants to merge 2 commits into
masterfrom
jferg-codex/explorer-metric-alert-context-rpc

Conversation

@JoshFerge
Copy link
Copy Markdown
Member

@JoshFerge JoshFerge commented May 11, 2026

Summary

  • Add optional metric_alert_context to Seer's Sentry RPC issue-details payload for metric issues.
  • Extract the context from serialized occurrence data so downstream agents can see alert aggregate, query, conditions, observed value, and detector/alert IDs.
  • Cover the new extraction and forwarding behavior in Seer agent tool tests.

Companion PR

Tests

  • .venv/bin/pytest -n0 -svv --reuse-db tests/sentry/seer/agent/test_tools.py -k "TestGetIssueDetails or TestGetIssueAndEventDetailsV2 or extract_metric_alert_context"
  • .venv/bin/prek run -q --files src/sentry/seer/agent/tools.py tests/sentry/seer/agent/test_tools.py
  • git diff --check

@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label May 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant