SLO-based alert routing (per-endpoint latency budgets)

[YaronZaki]

• Difficulty: intermediate · Effort: M · Priority: P3
• Impact: every alert
• Problem Statement
  Today Sentry fires on every error regardless of priority. A single
  user's /api/save-bug-report typo blows up in Sentry the same way
  as a global outage of /api/check-user.
• Why It Matters
  Alert fatigue desensitises operators. A read-endpoint 4xx is noise;
  an auth-mutation 5xx is a P0.
• Expected Outcome
  Per-endpoint SLO burned-rate alert rules in Sentry:
  • Auth/mutation routes: 99% success budget.
  • Read routes: 95% success budget.
  • /health, /metrics: no alerts (probe routes).
• Acceptance Criteria
  • Test synthesises a 1% error burst on /api/check-user; Sentry
    alert routes to #oncall-protocol (vs #oncall-fyi).
  • Read-route errors demote to info level.
• Implementation Notes
  Sentry's Alerts UI: Burn Rate, Window 1h and 6h. Code-readable
  thresholds in quantara/web_app/utils/sentry_alerts.yaml.
• Files / Modules Affected
  • new: quantara/web_app/utils/sentry_alerts.yaml
  • Sentry UI configuration
• Dependencies: standalone.

[Davichi-1]

Hi! This looks like something I can handle confidently. Kindly assign the issue to me if it’s still open.

[akinboyewaSamson]

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

[grantfox-oss]

🦊 GrantFox — @Davichi-1 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #299)
2. Your PR will be reviewed by the Quantarq maintainers

Good luck! Track your progress on GrantFox.