[
https://issues.apache.org/jira/browse/FELIX-6292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150913#comment-17150913
]
Amit Mondal commented on FELIX-6292:
------------------------------------
[~henzlerg] I think I misunderstood the way how _*HealthCheckMonitor*_ works. I
thought earlier that the health checks will be executed according to their
configured intervals or crons and _*HealthCheckMonitor*_ will only expose the
_*Healthy*_ and _*Unhealthy*_ service instances based on the type of the result
the health check reported.
But apparently _*HealthCheckMonitor*_ will execute the configured health checks
all together based on the interval or cron configuration of the monitor itself.
I am not sure if it would work to fulfill the use case I mentioned above. Do
you have any idea?
> 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)
