-
Health check timeouts can now be configured in
java.time.Duration
format. The timeouts can still be configured using millisecond values (long
) as well to stay compatible with old configurations. -
Dependency versions are now managed by
spring-boot-dependencies
. (ISSUE-17) -
As of now, cache metrics can be exposed. For this purpose, a corresponding MeterRegistry instance must be passed when instantiating the Kafka Health Check. (ISSUE-20)
-
The cache size can now be configured via the property
kafka.health.cache.maximum-size
. The default value for the cache size is 200. (ISSUE-22) -
Filtering messages that do not come from the same instance. (ISSUE-24)
-
Make consumer groups unique by appending a random UUID when no group ID is configured explicitly.
-
Refactor health check strategy: Kafka polled continuously.