You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While away at our developer retreat in December 2021, a report of missing dosage curations surfaced the issue that the 'gene-dosage-reader' kubernetes workload running on the production cluster was not producing output and had appeared to be running but stopped.
Research needs to be done to
determine what exception may have occurred that caused the reader to stop reading and producing
add some process monitoring beyond a simple liveness check
Whatever the appropriate solution is determined to be, it needs to have an alerting component for making dev/ops team aware of failures.
The text was updated successfully, but these errors were encountered:
While away at our developer retreat in December 2021, a report of missing dosage curations surfaced the issue that the 'gene-dosage-reader' kubernetes workload running on the production cluster was not producing output and had appeared to be running but stopped.
Research needs to be done to
Whatever the appropriate solution is determined to be, it needs to have an alerting component for making dev/ops team aware of failures.
The text was updated successfully, but these errors were encountered: