Skip to content

fix(formatting): read camelCase metric alert evidence and link to breach data #1715

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sentry-junior wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix(formatting): read camelCase metric alert evidence and link to breach data #1715

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a819d48
fix(formatting): read camelCase metric alert evidence and link to bre…
sentry-junior[bot] Oct 29, 2026
5dbee37
fix(formatting): group OR monitor queries before the environment filter
sentry-junior[bot] Oct 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/contributing/tool-responses.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,6 +125,14 @@ omits the section. Commit lookup is optional: failures do not prevent issue
details from loading, but unexpected server or response-validation failures
are reported to Sentry.

For metric issues, `Metric Alert Details` comes from the occurrence's
`evidenceData`, which the event API returns camelCased
(`dataSources[].queryObj.snubaQuery`, `detectorId`). It shows the Metric
Monitor ID, dataset, aggregate, query, interval, environment, evaluated window,
value, and threshold. Response Notes replace the stacktrace and trace hints with
`get_metric_monitor_details` and a pre-filled `search_errors`, `search_logs`,
`search_traces`, or `search_metrics` call for the monitor's query.

The event API's legacy `context` field (extra data) can be `null`. Issue details
must still load; omit the `Extra Data` section for null or empty values while
preserving the event's error, stacktrace, and structured `contexts` data.
Expand Down
Loading
Loading