Sentry issue investigation brief
Use “Sentry issue investigation brief” in Recued. It provides a read-only AI-assisted investigation brief for one Sentry issue.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (19 steps)
issue
?
events_raw
?
tag_values_raw
?
hashes_raw
?
defaults
defaults
Apply defaults
event_count
count
Count items in events
tag_value_count
count
Count items in tag values
hash_count
count
Count items in hashes
issue_summary
pick
Keep only specific fields from
event_rows
slice
Take a subset of
tag_rows
slice
Take a subset of
hash_rows
slice
Take a subset of
ai_event_rows
map
Extract from each item
ai_tag_rows
map
Extract from each item
ai_hash_rows
map
Extract from each item
summarize
?
event_table
to_table
Format results as a data table
tag_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
focus
setting
=
Summarize this Sentry issue for a developer/operator: user impact, status, recent evidence, likely affected surface, tag distribution, release hints, and concrete next debugging steps. Do not invent facts outside the Sentry data.
sentry
setting
=
tag key
setting
=
environment
issue id
setting
=
row limit
setting
=
20
max length
setting
=
900
stats period
setting
=
24h
organization id or slug
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.