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
The way the haystack-commons health check works is that when an uncaught exception occurs in Kafka, the health controller would write to a file indicating that the app is unhealthy, and then the k8s liveness check would see that and fail the health check.
We want something like this, but we need to coordinate it with #253 and #245. Ill-formatted metrics should now cause the health check to fail.
The text was updated successfully, but these errors were encountered:
The way the haystack-commons health check works is that when an uncaught exception occurs in Kafka, the health controller would write to a file indicating that the app is unhealthy, and then the k8s liveness check would see that and fail the health check.
We want something like this, but we need to coordinate it with #253 and #245. Ill-formatted metrics should now cause the health check to fail.
The text was updated successfully, but these errors were encountered: