Improved readiness probe #574
Closed
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.
Description
Current readiness probe couldn't detect configuration loading failures due to unresolved environment variables, because the application crashed before the probe endpoint was available. Also there were no validation of template placeholder resolution and no comprehensive application initialization tracking.
Enhanced readiness probe detects unresolved template placeholders using generic pattern matching, monitors initialization steps (config loading, llama client, MCP servers, etc.) while maintaining existing LLM provider health functionality. It also returns detailed reason in readiness probe response for troubleshooting.
Type of change
Related Tickets & Documents
Checklist before requesting a review
Testing
Tested by building and running local assisted-chat stack.
Readiness probe response when using bad config: (HTTP 503 Service Unavailable)
Same with proper config: