fix: remove intentional errors causing 500s on /ping endpoint #40
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
The current
/pingendpoint in the flow-test service intentionally raises an exception every third second, causing intermittent 500 Internal Server Errors. This behavior is triggering production alerts and impacting service readiness and monitoring.Changes Made
/pingendpoint inapp/main.py.Rationale
/pingendpoint is typically used as a health check and must consistently return successful responses.After applying this change, redeploy the application to resolve the production 500 error alert on
/ping. If error simulation is required, use feature flags or non-production environments.This is a minimal and safe change to address the root cause of the alert firing.