fix: remove deliberate exception from /ping endpoint to prevent 500 errors and alert firing #44
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes the issue causing high rates of HTTP 500 internal server errors on the
/pingendpoint of theflow-testworkload in thedemo-prodEKS cluster. The root cause was a deliberate exception-raising condition in theapp/main.pyfile that threw an error every 3 seconds, triggering alerts and impacting service reliability.Changes Made
/pingroute handler inapp/main.pyto prevent the deliberate exceptions.Rationale
Removing the deliberate exception resolves the internal server errors, stops the continuous alert firing in Prometheus/Grafana, and ensures the
/pingendpoint behaves as a healthy liveness probe returning a 200 status. The fix is minimal and aligns with the GitOps deployment model, maintaining service stability and observability with the Prometheus instrumentation.Please review and merge to restore stable, error-free operation on the
/pingendpoint.