Add slow-query alerting via pg_stat_statements threshold

[greatest0fallt1me]

Description

This is a backend issue for the GrantFox campaign. Background worker that polls pg_stat_statements and posts a webhook when any query exceeds threshold p95.

Requirements and Context

• Polls every 5 minutes
• Threshold from env
• Posts to webhook
• Dedup window per fingerprint
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b feature/slow-query-alerts

2. Implement changes
   • src/workers/slowQueryAlerter.ts (new)
   • docs/slow-query-alerts.md (new)
3. Test and commit
   • Run the repo's standard test suite and lint
   • Cover edge cases; include output in the PR

Example commit message

feat: alert on slow queries via pg_stat_statements

Acceptance Criteria

• Worker runs every 5m
• Threshold configurable
• Webhook fires
• Dedup works

Guidelines

• Minimum 90% test coverage on changed lines
• Input validation at the boundary; standardized error envelope
• Structured logging with correlation IDs
• Clear documentation and inline comments
• Timeframe: 96 hours

[Truphile]

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

Hi team, I’d love to be assigned to this issue.
As a returning contributor, I’m already well-acquainted with the project’s architectural boundaries, conventions, and CI/CD workflow. Having implemented very similar patterns in production before, I can deliver a clean, highly isolated solution that requires minimal review overhead and eliminates risk of architectural drift.
I’ve reviewed the acceptance criteria and am ready to open a targeted PR as soon as it's assigned. Thanks!

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

[oyinade247]

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

Assign me this pls

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

[BigJohn-dev]

@BigJohn-dev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to fix this ASAP

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

[grantfox-oss]

🦊 GrantFox — @BigJohn-dev has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.

[drips-wave]

Congratulations, @BigJohn-dev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @BigJohn-dev: 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 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@BigJohn-dev's PR #567 was approved and merged by @greatest0fallt1me.

🏆 @BigJohn-dev: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,111 total points). Track your full progress on GrantFox.

👏 Great work, @BigJohn-dev! Keep contributing to CalloraOrg.