Problem Statement
When building integrations that sync Sentry issues to external task trackers (Asana, Jira, etc.), manual priority changes in Sentry don't trigger any webhook. The only way to detect priority changes is expensive polling of all open issues.
Issue webhooks fire for: created, resolved, assigned, archived, unresolved. Auto-escalations trigger "unresolved" with substatus "escalating". But manual priority changes produce no webhook event.
Solution Brainstorm
Add a priority_changed action to issue webhooks, or include priority in the payload when it changes alongside other actions.
Product Area
Settings - Integrations
We want to define a set of lightweight metrics that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that do NOT overlap with Tracing. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.
Examples**:**
- Node.js runtime metrics (e.g., event loop delay, heap usage)
- Prisma-related metrics in Next.js
- Mobile CPU / memory usage to help surface potential ANRs or app hangs
Candidate Metrics (add more below)
(please also add ideas, questions or examples in comments)
Problem Statement
When building integrations that sync Sentry issues to external task trackers (Asana, Jira, etc.), manual priority changes in Sentry don't trigger any webhook. The only way to detect priority changes is expensive polling of all open issues.
Issue webhooks fire for: created, resolved, assigned, archived, unresolved. Auto-escalations trigger "unresolved" with substatus "escalating". But manual priority changes produce no webhook event.
Solution Brainstorm
Add a
priority_changedaction to issue webhooks, or include priority in the payload when it changes alongside other actions.Product Area
Settings - Integrations
We want to define a set of lightweight metrics that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that do NOT overlap with Tracing. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.
Examples**:**
Candidate Metrics (add more below)
(please also add ideas, questions or examples in comments)