This library provides a kafka health check for spring boot actuator.
Add the following dependency to your pom.xml
<dependency>
<groupId>com.deviceinsight.kafka</groupId>
<artifactId>kafka-health-check</artifactId>
<version>1.3.0</version>
</dependency>In the same maven module you can configure the topic, poll timeouts, subscription timeouts and the receive timeouts
in the application.yml
An example for an application.yaml is:
kafka:
health:
topic: health-checks
sendReceiveTimeout: 2.5s
pollTimeout: 200ms
subscriptionTimeout: 5sThe values shown are the defaults.
|
Important
|
Make sure the configured health check topic exists! |
@Bean
@ConfigurationProperties("kafka.health")
public KafkaHealthProperties kafkaHealthProperties() {
return new KafkaHealthProperties();
}@Bean
public KafkaConsumingHealthIndicator kafkaConsumingHealthIndicator(KafkaHealthProperties kafkaProperties,
KafkaProperties processingProperties) {
return new KafkaConsumingHealthIndicator(kafkaHealthProperties, processingProperties.buildConsumerProperties(),
processingProperties.buildProducerProperties());
}Now if you call the actuator endpoint actuator/health you should see the following output:
{
"status" : "UP",
"details" : {
"kafkaConsuming" : {
"status" : "UP"
}
}
}| Property | Default | Description |
|---|---|---|
kafka.health.topic |
|
Topic to subscribe to |
kafka.health.sendReceiveTimeout |
2.5s |
The maximum time, given as Duration, to wait for sending and receiving the message. |
kafka.health.pollTimeout |
200ms |
The time, given as Duration, spent fetching the data from the topic |
kafka.health.subscriptionTimeout |
5s |
The maximum time, given as Duration, to wait for subscribing to topic |
kafka.health.cache.maximumSize |
200 |
Specifies the maximum number of entries the cache may contain. |
Creating a new release involves the following steps:
-
./mvnw gitflow:release-start gitflow:release-finish -
git push origin master -
git push --tags -
git push origin develop
In order to deploy the release to Maven Central, you need to create an account at https://issues.sonatype.org and
configure your account in ~/.m2/settings.xml:
<settings>
<servers>
<server>
<id>ossrh</id>
<username>your-jira-id</username>
<password>your-jira-pwd</password>
</server>
</servers>
</settings>The account also needs access to the project on Maven Central. This can be requested by another project member.
Then check out the release you want to deploy (git checkout x.y.z) and run ./mvnw deploy -Prelease.