Describe the Bug
Database status is not being actively monitored or polled when running command 'npm run docker:watch' which enables run of docker with view of docker output logs. These output logs contain useful information and insights on service-image health and maintenance statuses.
At present, only observable activity that comes from PostgreSQL’s are the internal checkpoint processes. These checkpoints are routine maintenance operations to flush dirty shared buffers to disk and record recovery points. While they help improve crash recovery time and system reliability, these checkpoint operations run typically every few minutes, they do not provide a reliable indication of database availability or readiness and so we need a true explicit postgres health check.
Expected Behavior:
A dedicated liveness/readiness health check is implemented to directly verify the availability of the database (e.g., via connection or query), ensuring accurate status reporting within Docker.
Steps to Reproduce
- Run setup script with 'setup-macos-linux.sh' or 'setup-windows.bat'.
- Run docker in watch mode with this command
npm run docker:watch.
- While in docker watch mode, notice no visible checks on postgres-dev database are appearing while regular checks on nestjs, nextjs are done.
Expected Behavior
The database container should be polled for health status at a frequency consistent with the nestjs-dev and nextjs-dev containers to ensure uniform monitoring across services.
Visual Aids
Expand ⬇️
Describe the Bug
Database status is not being actively monitored or polled when running command 'npm run docker:watch' which enables run of docker with view of docker output logs. These output logs contain useful information and insights on service-image health and maintenance statuses.
At present, only observable activity that comes from PostgreSQL’s are the internal checkpoint processes. These checkpoints are routine maintenance operations to flush dirty shared buffers to disk and record recovery points. While they help improve crash recovery time and system reliability, these checkpoint operations run typically every few minutes, they do not provide a reliable indication of database availability or readiness and so we need a true explicit postgres health check.
Expected Behavior:
A dedicated liveness/readiness health check is implemented to directly verify the availability of the database (e.g., via connection or query), ensuring accurate status reporting within Docker.
Steps to Reproduce
npm run docker:watch.Expected Behavior
The database container should be polled for health status at a frequency consistent with the nestjs-dev and nextjs-dev containers to ensure uniform monitoring across services.
Visual Aids
Expand ⬇️