Hi Okay this was several hours of work, but the changes are tested as PR and merged to the main branch.
The migration guide has details on this change, and you can also see in the general health-check doc page more details. In a nutshell you can also enable all producer checks globally via camel.health.producers-enabled = true This is similar, how you can enable/disable other types of checks such as for consumers. In the same work then producer health checks are more similar to consumers, as they are also prefixed with producer:xxx like consumers are via consumer:xxx. This makes it also possible to exclude via patterns. On Fri, Jul 28, 2023 at 11:24 AM Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > See ticket > https://issues.apache.org/jira/browse/CAMEL-19645 > > We have health checks for components that have producers, mainly for the > AWS components and then for camel-kafka as well. > > However for AWS they have been not working for a while and has been not > included in the releases. > > To keep this behavior we could keep the health checks for producers > disabled by default. > This only affects camel-kafka where it would be disabled now. > > You can turn this on via > > camel.component.kafka.health-check-producer-enabled = true > > The health checks has most value for consumers where they assist during > startup to signal when Camel is started healthy and is ready to > accept incoming traffic. > > For producers then Camel already have error handling to retry calling a > downstream service. > > If a producer is enabled and a downstream service for some reason is not > live, then with health checks enabled, then the Camel application will be > reported as DOWN, > > > > > -- > Claus Ibsen > ----------------- > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen ----------------- @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
