[jira] [Resolved] (SLING-3034) Check contents of healtchecks bundle

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz resolved SLING-3034.
----------------------------------------

    Resolution: Fixed

Health Check Tools initial release done in SLING-3127

> Check contents of healtchecks bundle
> ------------------------------------
>
>                 Key: SLING-3034
>                 URL: https://issues.apache.org/jira/browse/SLING-3034
>             Project: Sling
>          Issue Type: Task
>          Components: Health Check
>            Reporter: Carsten Ziegeler
>            Assignee: Bertrand Delacretaz
>             Fix For: Health Check core 1.0.4
>
>
> The current healtchecks bundle seems to be a collection of completely different things. I think we should reduce this to the bare minimum as these services are API.
> I think the CompositeHealthCheck is fine, as well as the ScriptableHealthCheck and the JmxAttributeHealthCheck.
> But I think the DefaultLoginsHealthCheck and the SlingRequestStatusHealthCheck should rather be moved out. Checking this stuff might look nice, but it imho it doesn't really provide a huge value. If you want to check the status of a request than you have to go all the way, the client browser would go. Otherwise your server looks fine but still a user does not get anything.
> The OsgiScriptBinding looks like a sample to me, we should rather remove this for now. Bundle information should be availabel as jmx info anyway.
> All services are configuration factories (which is good) but set the name to "org.apache.sling.hc.{classname}". I think we should use the real package name here, I see no good reason to use some fake package name



--
This message was sent by Atlassian JIRA
(v6.1#6144)