Error Rate Alerting Rules

[DokaIzk]

Title: feat: add error rate alerts to monitoring system

Labels: observability alerting
Complexity: medium

Description:
Create alerting rules for error rate thresholds:

• Alert if error rate > 1%
• Alert if error rate > 5% (critical)
• Include service in alert
• Include error message breakdown

Acceptance Criteria:

• Error rate alerts configured
• Thresholds based on SLA
• Alerts include root cause info
• Tests verify alert rules

---

[Habi-tec]

@Habi-tec has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I'd be glad to handle this issue. I'll keep the implementation concise, maintainable, and well-documented.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Habi-tec to this issue.

[trinnode]

@trinnode has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer! Can I work on this issue!
Thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @trinnode to this issue.

[drips-wave]

Congratulations, @trinnode! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @trinnode: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @trinnode as part of the Stellar Wave Program's 8th Wave 🥳

Moderator's reason: [Auto-assessed] The PR #1384 was successfully merged by maintainers on 2026-08-29, and it comprehensively addresses Issue #1294 by implementing error rate alerting rules with SLA-based thresholds (>1% warning and >5% critical), service groupings, root-cause queries, and a corresponding test suite.

😎 @trinnode: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.