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
We have a situation where we would like to execute only a set of specific health checks depending on the incoming REST call. This is because we run multiple tenants on the same instance and would like to show only "tenant A"-relevant health checks if the request runs in the context of "tenant A." On the other hand, we would like to see all health checks if there is no tenant-specific context.
Registering/unregistering health checks inside of a Vertx router filter is not an option, as it seems hacky and mainly beacuse this changes the configuration of the system rather than only being effective for the current request.
SUGGESTION: A new interface ConditionalHealthCheck which extends HealthCheck that holds an additional method, e.g., boolean runCheck(). The Health Registry can then check if a health check needs to be executed or not.
The text was updated successfully, but these errors were encountered:
We have a situation where we would like to execute only a set of specific health checks depending on the incoming REST call. This is because we run multiple tenants on the same instance and would like to show only "tenant A"-relevant health checks if the request runs in the context of "tenant A." On the other hand, we would like to see all health checks if there is no tenant-specific context.
Registering/unregistering health checks inside of a Vertx router filter is not an option, as it seems hacky and mainly beacuse this changes the configuration of the system rather than only being effective for the current request.
SUGGESTION: A new interface
ConditionalHealthCheck
which extendsHealthCheck
that holds an additional method, e.g.,boolean runCheck(
). The Health Registry can then check if a health check needs to be executed or not.The text was updated successfully, but these errors were encountered: