Introduce health-check granularity for downstream dependencies

[Baskarayelu]

Introduce health-check granularity for downstream dependencies

Description

• Expand health endpoint to report readiness of DB, cache, queue, and third-party gateway connectivity.

Requirements and context

• Keep liveness endpoint lightweight and independent from downstream checks.
• Expose dependency statuses without secret details.

Suggested execution

• Add dedicated readiness probes with timeout budgets.
• Return summarized status object with per-dependency state.

Test and commit

• Add tests for degraded dependency state and timeout handling.

Example commit message

• enhance(health): add readiness checks for backend dependencies

Guidelines

• Do not block event loop with synchronous checks.
• Keep probe cost predictable under load.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Danto1606]

@Danto1606 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I would like to work on this please

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

[drips-wave]

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

🧑‍💻 @Danto1606: 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 @Danto1606 as part of the Stellar Wave Program's 3rd Wave 🥳

Moderator's reason: [Auto-assessed] The contributor successfully implemented the requested health-check granularity for DB, cache, queue, and third-party gateways, including the required tests and logic for liveness vs. readiness probes. The PR (#196 in Credence-Backend) was recently merged by the maintainers, directly addressing the requirements of the issue.

😎 @Danto1606: 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.