Health endpoint uses circuit breaker state instead of pinging Redis

[hman38705]

Labels: reliability, api, monitoring

Priority: High

Description

The health endpoint reports Redis as healthy based on the in-memory circuit breaker state (which is fail-open). A Redis restart that has not yet tripped the breaker will be reported as healthy even though connections are failing.

Acceptance Criteria

• Add an explicit Redis PING command in the /health/ready handler
• Report Redis as degraded (not just down) if the ping succeeds but latency exceeds 100 ms
• Expose a /health/dependencies endpoint returning structured JSON with each dependency name, status, and latency
• Add a test that mocks a Redis ping timeout and verifies the health endpoint returns 503

[Killerjunior]

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

Hi, I would love to work on this issue. Kindly assign.

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

[0xElyte]

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

I'd love to resolve this issue fast

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

[YfengJ]

Hi maintainers, I would like to work on this issue if it is still available. If assigned, I will keep the change focused on health readiness: add an explicit Redis PING path with latency measurement, return structured dependency status JSON, and cover timeout/degraded cases in tests without touching unrelated API behavior.

[Inkman007]

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

. If assigned, I will provide consistent progress updates and a well-tested implementation.

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

[Caneryy]

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

Hi there, can I work on this issue?

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

[drips-wave]

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

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

[YfengJ]

Thanks for the update. I see this has been assigned to @Inkman007, so I’ll step back and avoid duplicating work.