Add structured log for database query exceeding 200ms response time

[Chucks1093]

Summary

Slow database queries are currently invisible until they surface as high API latency. A warning log should be emitted whenever a query takes longer than 200ms so slow queries can be identified and optimised before they impact users.

Scope

• Instrument the database query layer to measure query duration
• Emit a warn-level log when duration exceeds 200ms with fields: query_name, duration_ms, table, operation (select/insert/update/delete)
• Log should not include query parameters to avoid leaking sensitive data
• Threshold should be configurable via an environment variable defaulting to 200

Acceptance Criteria

• Warning log emitted when query exceeds threshold
• Log not emitted for queries below threshold
• All four fields present in the log
• Query parameters absent from log output
• Threshold configurable via environment variable

ETA: 12 hours

---

Coordinate on Telegram

[OkeQueen]

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

Hi Chief Maintainer, I'd like to work on this if it's still available.

I've read the issue and have a reasonable understanding of the work involved. I'd start by reproducing the behavior locally and confirming it still occurs on main, then work back to the underlying cause before making any changes.

The PR would include tests for the described case, a check that existing behavior is unaffected, and documentation updates where relevant.

I'll follow the repo's contribution guidelines and keep this thread updated. If I run into anything ambiguous, I'll ask here rather than guess and go in the wrong direction.

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

[Fury03]

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

I'd like to work on this issue. I've reviewed the requirements and have a clear implementation plan. If assigned, I'll submit a high-quality PR that follows the project's guidelines.

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

[circleboyslimited]

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

I can work on this

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

[heymariam]

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

Hello Maintainer, I’d to work on this issue. assign it to me so i can start working on it

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

[michealross]

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

I have a solid understanding of the underlining architecture required for this task and am ready to start testing a solution immediately.

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

[drips-wave]

Congratulations, @circleboyslimited! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @circleboyslimited: 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 completed by @circleboyslimited as part of the Stellar Wave Program's 7th Wave 🥳

😎 @circleboyslimited: 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. You can also Leave a review to share your experience working on this issue.

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