[jira] [Resolved] (CAMEL-15134) camel health - Remove HealthCheckRepository and routes check

["Claus Ibsen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-15134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-15134.
---------------------------------
    Resolution: Won't Fix

Okay so the trick was that we needed a new HealthCheck per route to make it fine grained in the reporting, and not a single HealthCheck class for all the routes. The latter would be too coarse grained, as a check per routes allows to report builder with details per route in the same key - route.id = foo.

But we can remove the JMX evaluators as its the job of the monitoring tools to setup rules.

> camel health - Remove HealthCheckRepository and routes check
> ------------------------------------------------------------
>
>                 Key: CAMEL-15134
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15134
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.4.0
>
>
> Lets simplify the health check api and the default implementations.
> The routes check is overlapping what monitoring systems can do by checking and reporting on metrics, such as if N errors within last Y minute then YELLOW etc.
> This job is better handled by those tools, than Camel.
> So the health checks become a basic API that are invoked on demand (ala spring boot acutators).
> And then we only need one kind of registry so removing the additional repository layer.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)