[
https://issues.apache.org/jira/browse/FELIX-6292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150757#comment-17150757
]
Georg Henzler edited comment on FELIX-6292 at 7/3/20, 6:15 AM:
---------------------------------------------------------------
For these kind of use cases FELIX-6250 "Introduce HealthCheckMonitor to keep
track of HC status and to register Condition Services, OSGi events, etc.
Edit CommentAssign" was created (and fixed already). That way execution and
result consumption is nicely decoupled. A very simple setup would
* Create a HC with a tag "foo" (can be via config or custom code)
* Create a HealthCheckMonitor for tag "foo" (config, see
[docu|https://github.com/apache/felix-dev/blob/master/healthcheck/README.md#setting-up-a-monitor-configuration])
* Create custom code to listen to OSGi events that the monitor emits and react
[~amitmondal] Please check if this approach works for you. ATM the event is
only sent if the status changes, maybe an option to always send the events
could be useful for you if you needed to send "every tick" no matter if it has
changed or not)
was (Author: henzlerg):
For these kind of use cases FELIX-6250 "Introduce HealthCheckMonitor to keep
track of HC status and to register Condition Services, OSGi events, etc.
Edit CommentAssign" was created (and fixed already). That way execution and
result consumption is nicely decoupled. A very simple setup would
* Create a HC with a tag "foo" (can be via config or custom code)
* Create a HealthCheckMonitor for tag "foo" (config, see
[docu|https://github.com/apache/felix-dev/blob/master/healthcheck/README.md#setting-up-a-monitor-configuration]
* Create custom code to listen to OSGi events that the monitor emits and react
[~amitmondal] Please check if this approach works for you.
> 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)
