You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/01/18 15:35:33 UTC

[GitHub] [camel] jamesnetherton commented on pull request #6779: CAMEL-17426: Prevent MicroProfile Health conflicting health data

jamesnetherton commented on pull request #6779:
URL: https://github.com/apache/camel/pull/6779#issuecomment-1015531508


   > I could see the case where the user checks the error, fixes it, then expect her/his application to run, but realises another error gets reported
   
   True... and this is pretty much a continuation of what happened before where all Camel health check results were aggregated. 
   
   > I realise that may not be trivial to report the list of errors, but that's not impossible :)
   
   If SmallRye Health made it possible to structure the values of the `data` element, then you could report additional error elements pretty easily (E.g as maps or arrays). But that's not currently possible. 
   
   So I guess you're left with the options of either combining & delimiting all of the error data in a single string (not great for human readability) or not aggregating the results of the routes / consumers checks (which I'd prefer to avoid due to the potential verbosity of reporting them as individual items). 
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org