[
https://issues.apache.org/jira/browse/CAMEL-17138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435287#comment-17435287
]
Antonin Stefanutti commented on CAMEL-17138:
--------------------------------------------
[~Federico Mariani] awesome! It looks good. My understanding is that only few
use cases populate the error at the moment, mainly when an exception occurs
while a route starts:
https://github.com/apache/camel/blob/617e150d1d6ac6c453fbb0239960c1c5b3f1a46d/core/camel-base-engine/src/main/java/org/apache/camel/impl/engine/AbstractCamelContext.java#L1209.
Populating the error for a larger set of cases should be addressed within the
scope of the following issues:
* CAMEL-16975
* CAMEL-16976
* CAMEL-16977
> Propagate error details from Camel health to MicroProfile Health
> ----------------------------------------------------------------
>
> Key: CAMEL-17138
> URL: https://issues.apache.org/jira/browse/CAMEL-17138
> Project: Camel
> Issue Type: Improvement
> Reporter: Antonin Stefanutti
> Priority: Major
> Fix For: 3.13.0
>
>
> The {{org.apache.camel.health.HealthCheck.Result}} interface exposes the
> {{Optional<Throwable> getError()}} method, that provides the exception
> information that may explain the health check result.
> This can prove very useful information for users. However, it is not
> propagated to the MicroProfile Health response
> {{org.eclipse.microprofile.health.HealthCheckResponse}}, that's converted
> from the Camel health check result.
> If the optional error is present, it should be propagated and accessible from
> the {{Optional<Map<String, Object>> HealthCheckResponse.getData()}} API.
> Other details could also be propagated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
