Skip to content

Releases: kumuluz/kumuluzee-health

v2.4.4

30 Nov 13:12
Compare
Choose a tag to compare

This patch release fixes a initialization bug, where built-in health checks were not initialized from configuration.

Bugs:

  • Fixed built-in health check configuration detection - use getMapKeys and getListSize instead of yaml-specific Map/List detection, that was removed in KumuluzEE 4.1.0

v2.4.3

06 Dec 06:59
Compare
Choose a tag to compare

This patch release fixes a bug, where health status was incorrectly reported as UP, even if on of the datasource health checks was DOWN.

Bugs:

  • Set datasource health check down on check connection.

v2.4.2

08 Jul 12:11
Compare
Choose a tag to compare

This patch release is a re-release of version 2.4.1, because the version 2.4.1 was not uploaded to Maven central. No changes in code were introduced.

v2.4.1

01 Jul 06:16
Compare
Choose a tag to compare

This patch release improves on existing DataSourceHealthCheck by adding support for multiple datasources.
Refer to the README for more information.

v2.4.0

13 Nov 14:15
Compare
Choose a tag to compare

We are happy to announce the release of KumuluzEE Health 2.4.0! This release updates the KafkaHealthCheck and allows you to specify additional client properties (see CONFGIGURATION). Additionally this release improves the existing OpenAPI-MP integration with the support for the kumuluzee-openapi-mp-maven-plugin.

Enhancements:

  • Allow additional client properties in KafkaHealthCheck.

Bugs:

  • Fixed OpenAPI integration bug, caused by SmallRye upgrade.

v2.3.1

03 Nov 07:13
Compare
Choose a tag to compare

This is a patch release fixing a bug with OpenAPI integration.

Bugs:

  • Fixed OpenAPI integration bug, caused by SmallRye upgrade.

v2.3.0

02 Nov 11:18
Compare
Choose a tag to compare

We are happy to announce the release of KumuluzEE Health 2.3.0! This release brings a new health check for Kafka clusters, integration with KumuluzEE OpenAPI MP and a minor bugfix.

The new health check allows you to monitor the health status of your Kafka cluster. To use it add the kafka-clients dependency (already included in kumuluzee-streaming) and activate it in the configuration framework. For example in config.yml:

kumuluzee:
  health:
    checks:
      kafka-health-check:
        bootstrap-servers: localhost:9095,localhost:9096,localhost:9097
        minimum-available-nodes: 2
        request-timeout-ms: 1000

For more information see README.

We have integrated KumuluzEE Health with KumuluzEE OpenAPI MP extension. You can now add /health, /health/ready and /health/live endpoints to OpenAPI schema by activating the integration in the configuration framework. For example in config.yml:

kumuluzee:
  health:
    openapi-mp:
      enabled: true

Features:

  • Added a new health check implementation: KafkaHealthCheck

Enhancements:

  • Added integration with KumuluzEE OpenAPI MP

Bugs:

  • Fixed NON_NULL serialization bug

v2.2.0

12 Mar 12:47
Compare
Choose a tag to compare

This version implements the MicroProfile Health 2.2 specification.

v2.1.1

24 Jan 13:41
Compare
Choose a tag to compare

This patch release fixes the problem with health checks configured with type: both.

v2.1.0

22 Nov 07:39
Compare
Choose a tag to compare

We are happy to announce a new version of the KumuluzEE Health. This version implements the MicroProfile Health 2.1 specification.

Features

  • Disabling default vendor procedures
    An implementation is allowed to supply a reasonable default (out-of-the-box) procedures as defined in the Health Check Procedures section. To disable all default vendor procedures, users can specify a MicroProfile Config configuration property mp.health.disable-default-procedures to true. This allows the application to process and display only the user-defined health check procedures.

Bugs

  • Fixed a bug in health check registration by name where name did not respect multiple lambda expressions within single bean.