[
https://issues.apache.org/jira/browse/FELIX-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17097881#comment-17097881
]
Georg Henzler commented on FELIX-4678:
--------------------------------------
Now with the Health Checks being available directly in Felix, the Event Admin
module itself could contain a health check (probably configurable on what
blacklisted event topics would lead to a CRITICAL status and what event topics
would only lead to a WARN result). The dependency to package
org.apache.felix.hc.api should be optional so if the HC api bundle is not
available, only the HC is not available but everything else works as usual.
> No list of blacklisted services available
> -----------------------------------------
>
> Key: FELIX-4678
> URL: https://issues.apache.org/jira/browse/FELIX-4678
> Project: Felix
> Issue Type: Improvement
> Components: Event Admin
> Affects Versions: eventadmin-1.4.2
> Reporter: Jörg Hoh
> Assignee: Jean-Baptiste Onofré
> Priority: Major
>
> When a service gets blacklisted by the eventAdmin, there is only a single
> warn statement in the logs. It would be great, if it would be an error, as a
> blacklisted service normally results in application problems. And if it's
> printed as error, it should be catched by any log analyzing mechanism.
> On top it would be good, if blacklisted services can be detected by a
> different way (e.g. by throwing an OSGI event, updating an JMX MBean or
> something like that). Log parsing is cumbersome if you need to do online
> monitoring of your application.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
