[
https://issues.apache.org/jira/browse/FELIX-6292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152070#comment-17152070
]
Georg Henzler commented on FELIX-6292:
--------------------------------------
[~amitmondal] IMHO the right way to setup your four checks is to
* Declare them as regular health checks without async executions
** hc.async.* properties were introduced to allow for long-running health
checks that would otherwise show up as timed out
* Create for each of the 4 health checks a monitor (it's a configuration
factory) to trigger it at the given schedule
* Define 4 custom or 1 generic event listener (choose the topic accordingly) to
process the results as given by the 4 given schedules
So the above mentioned requirement is already working in the current version, I
would not introduce more complexity here (as said, IMHO it is good to have the
checks itself decoupled from processing the results).
> Introduce functionality to perform custom operation after a heath check is
> executed
> -----------------------------------------------------------------------------------
>
> Key: FELIX-6292
> URL: https://issues.apache.org/jira/browse/FELIX-6292
> Project: Felix
> Issue Type: New Feature
> Components: Health Checks
> Reporter: Amit Mondal
> Priority: Minor
> Labels: ready-to-commit
>
> Sometimes consumers need to perform custom operations after a health check
> gets executed. For example, one might need to send the health check result to
> online monitoring system such as Kibana, Grafana etc. That's why we need to
> introduce an extension point for consumers to extend the current
> functionality.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
