2019-03-28 18:35:14 +03:00
|
|
|
= KafkaHealthCheck
|
|
|
|
|
:icons: font
|
|
|
|
|
|
2019-12-05 19:32:14 +03:00
|
|
|
== Version 1.3.0
|
2019-10-10 21:33:20 +03:00
|
|
|
|
2019-12-05 19:32:14 +03:00
|
|
|
* 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.
|
2021-02-08 11:56:29 +03:00
|
|
|
* Dependency versions are now managed by `spring-boot-dependencies`.
|
|
|
|
|
(https://github.com/deviceinsight/kafka-health-check/issues/17[ISSUE-17])
|
2021-04-13 10:36:26 +03:00
|
|
|
* As of now, cache metrics can be exposed. For this purpose, a corresponding MeterRegistry instance must be passed
|
|
|
|
|
when instantiating the Kafka Health Check. (https://github.com/deviceinsight/kafka-health-check/issues/20[ISSUE-20])
|
2021-04-14 09:38:52 +03:00
|
|
|
* The cache size can now be configured via the property `kafka.health.cache.maximum-size`.
|
2021-04-13 11:22:47 +03:00
|
|
|
The default value for the cache size is 200. (https://github.com/deviceinsight/kafka-health-check/issues/22[ISSUE-22])
|
2021-04-13 12:56:23 +03:00
|
|
|
* Filtering messages that do not come from the same instance.
|
|
|
|
|
(https://github.com/deviceinsight/kafka-health-check/issues/24[ISSUE-24])
|
2019-12-05 19:32:14 +03:00
|
|
|
|
|
|
|
|
== Version 1.2.0
|
|
|
|
|
|
|
|
|
|
* Reduce logging level of health check calls to `TRACE`.
|
2019-10-10 21:33:20 +03:00
|
|
|
|
2019-05-15 17:23:27 +03:00
|
|
|
== Version 1.1.0
|
|
|
|
|
|
2019-05-24 14:02:45 +03:00
|
|
|
* Make consumer groups unique by appending a random UUID when no group ID is configured explicitly.
|
2019-05-16 10:25:22 +03:00
|
|
|
* Refactor health check strategy: Kafka polled continuously.
|
2019-05-15 17:23:27 +03:00
|
|
|
|
2019-05-16 10:25:22 +03:00
|
|
|
== Version 1.0.0
|
2019-03-28 18:35:14 +03:00
|
|
|
|
|
|
|
|
* Develop kafka health check
|
