Description
Operational visibility requires a deep health check endpoint (GET /health/deep) that assesses backend subsystems including PostgreSQL connectivity via Prisma, Stellar Horizon RPC responsiveness, and worker processing state before reporting overall node status.
Context & Requirements
- Endpoint location:
GET /health/deep in src/routes/health.ts.
- Checks required:
- Database: Simple query ping via Prisma (
prisma.$queryRaw).
- Stellar Horizon: Fetch latest ledger sequence or network root endpoint response time.
- Environment/Worker: Check uptime and configuration state.
- Response must return status 200 OK if all critical services respond, or 503 Service Unavailable if key dependencies fail.
Acceptance Criteria
Implementation Guidance
- Keep individual check timeouts reasonable (e.g., 3-5 seconds) so health probes do not hang.
- Avoid exposing sensitive operational secrets or internal connection strings in response output.
- Follow Fastify schema definitions for response serialization.
Testing & Validation
- Run tests with
npm test.
- Validate that mock DB or Horizon failures correctly result in a 503 response code.
Submission Guidelines
- Open a PR that includes "Closes #".
- Ensure task assignment before starting work.
- Maintain existing code structure and linting requirements.
Wave complexity: Medium
Description
Operational visibility requires a deep health check endpoint (
GET /health/deep) that assesses backend subsystems including PostgreSQL connectivity via Prisma, Stellar Horizon RPC responsiveness, and worker processing state before reporting overall node status.Context & Requirements
GET /health/deepinsrc/routes/health.ts.prisma.$queryRaw).Acceptance Criteria
GET /health/deeproute insrc/routes/health.ts.Implementation Guidance
Testing & Validation
npm test.Submission Guidelines
Wave complexity: Medium