/healthy
. This path can be used as a liveness probe from within your orchestration platform of choice./healthy
endpoint returns a 200
status code if the kPow instance is healthy. /healthy
endpoint returns a 503
status code if the kPow instance is unhealthy (see: Error states + strategies)/healthy
endpoint does not require any user authentication to access. /up
endpoint can be used for readiness probes. It always returns a 200
status when kPow's HTTP server is up and reachable.ERROR
state in certain scenarios where a Kafka Cluster becomes unavailable for a duration longer than the configured timeout+heartbeat. STREAMS_ERROR_STRATEGY
environment variable to handle this scenario. Possible strategies include:LOG_EXCEPTION
- default, logs an error. Note: once kPow enters this ERROR state, snapshotting will continue, but the UI will be unavailable until the instance has been manually restarted.LOG_AND_EXIT
- logs an error and exits the kPow process with a status code of 1
LOG_AND_EXIT
strategy. However, in scenarios such as deploying a JAR to an EC2 instance, configuring this strategy may be desirable.HTTP_FORWARDED=true
in conjunction with Jetty Authentication or when terminating SSL at a proxy to ensure that redirects maintain the correct connection scheme.PORT
(default: 3000). /kpow
. This scenario might be useful if your company has a suite of tools that you want to have grouped at a single host.http://kpow.info/kpow
nginx.conf
/kpow
. This scenario might be useful if your company has a suite of tools that you want to have grouped at a single HTTP endpoint.