[
https://issues.apache.org/jira/browse/FELIX-6292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151127#comment-17151127
]
Georg Henzler edited comment on FELIX-6292 at 7/3/20, 9:58 PM:
---------------------------------------------------------------
So HealthCheckMonitor will execute each tag/name as listed in the configuration
and send events for it. I updated the documentation (and also made it a little
bit more flexible to allow to either post events only for status changes or for
all runs as triggered by HealthCheckMonitor):
https://github.com/apache/felix-dev/blob/master/healthcheck/README.md#osgi-events-for-health-check-status-changes-and-updates
With the event listener you have full access to the execution result which
should satisfy your use case.
was (Author: henzlerg):
So HealthCheckMonitor will execute each tag/name as listed in the configuration
and send events for it. I updated the documentation (and also make it a little
bit more flexible to allow to either post events only for status changes or for
all runs as triggered by HealthCheckMonitor):
https://github.com/apache/felix-dev/blob/master/healthcheck/README.md#osgi-events-for-health-check-status-changes-and-updates
With the event listener you have full access to the execution result which
should satisfy your use case.
> 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)
