Compare commits
11 Commits
703eb03e43
...
826458f91f
Author | SHA1 | Date |
---|---|---|
bvn13 | 826458f91f | |
bvn13 | 460b9d6ac3 | |
bvn13 | 3298642929 | |
bvn13 | 0850e9854e | |
bvn13 | d23de17047 | |
bvn13 | 37a1716280 | |
bvn13 | 501944c8ff | |
bvn13 | ed0de137a1 | |
bvn13 | 32e1e5fc8d | |
bvn13 | 0d1e544bd5 | |
bvn13 | ca96259f19 |
|
@ -10,7 +10,7 @@ Add the following dependency to your `pom.xml`
|
|||
|
||||
```xml
|
||||
<dependency>
|
||||
<groupId>com.deviceinsight.kafka</groupId>
|
||||
<groupId>me.bvn13.kafka.health</groupId>
|
||||
<artifactId>kafka-health-check</artifactId>
|
||||
<version>1.4.0</version>
|
||||
</dependency>
|
||||
|
|
|
@ -1,28 +0,0 @@
|
|||
= KafkaHealthCheck
|
||||
:icons: font
|
||||
|
||||
== Version 1.3.0
|
||||
|
||||
* 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`.
|
||||
(https://github.com/deviceinsight/kafka-health-check/issues/17[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. (https://github.com/deviceinsight/kafka-health-check/issues/20[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. (https://github.com/deviceinsight/kafka-health-check/issues/22[ISSUE-22])
|
||||
* Filtering messages that do not come from the same instance.
|
||||
(https://github.com/deviceinsight/kafka-health-check/issues/24[ISSUE-24])
|
||||
|
||||
== Version 1.2.0
|
||||
|
||||
* Reduce logging level of health check calls to `TRACE`.
|
||||
|
||||
== Version 1.1.0
|
||||
|
||||
* Make consumer groups unique by appending a random UUID when no group ID is configured explicitly.
|
||||
* Refactor health check strategy: Kafka polled continuously.
|
||||
|
||||
== Version 1.0.0
|
||||
|
||||
* Develop kafka health check
|
|
@ -0,0 +1,29 @@
|
|||
# KafkaHealthCheck
|
||||
|
||||
## Version 1.4.0
|
||||
|
||||
* Got rid of `subscriptionTimeout` as a redundant timeout
|
||||
* Changed maven group publication: switched into `me.bvn13.kafka.health`
|
||||
|
||||
## Version 1.3.0
|
||||
|
||||
* 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](https://github.com/deviceinsight/kafka-health-check/issues/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](https://github.com/deviceinsight/kafka-health-check/issues/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](https://github.com/deviceinsight/kafka-health-check/issues/22)
|
||||
* Filtering messages that do not come from the same instance. [ISSUE-24](https://github.com/deviceinsight/kafka-health-check/issues/24)
|
||||
|
||||
## Version 1.2.0
|
||||
|
||||
* Reduce logging level of health check calls to `TRACE`.
|
||||
|
||||
## Version 1.1.0
|
||||
|
||||
* Make consumer groups unique by appending a random UUID when no group ID is configured explicitly.
|
||||
* Refactor health check strategy: Kafka polled continuously.
|
||||
|
||||
## Version 1.0.0
|
||||
|
||||
* Develop kafka health check
|
Loading…
Reference in New Issue