[
https://issues.apache.org/jira/browse/SLING-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-2822.
----------------------------------------
Resolution: Fixed
Health Check Tools initial release done in SLING-3127
> Extensible Sling system health checking tool
> --------------------------------------------
>
> Key: SLING-2822
> URL: https://issues.apache.org/jira/browse/SLING-2822
> Project: Sling
> Issue Type: Improvement
> Components: Health Check
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Attachments: nodes.json, nodes.json, setup.bash
>
>
> I have created a prototype at https://github.com/bdelacretaz/muppet-prototype
> that we might want to move to our contrib folder.
> Muppet (it's like a Puppet, but different (*)) allows you to check the health
> of a system by defining rules that (out of the box) verify things like the
> presence of specific OSGi bundles, JMX MBeans values, JUnit tests execution
> (including scriptable ones thanks to the Sling testing tools), correct
> disabling of default Sling credentials, etc.
> New rule types can be defined by adding RuleBuilder OSGi services, there are
> several examples in this initial code.
> I'll add a how-to for this initial version here.
> Known issues are:
> -The output does not indicate the value that causes a rule to fail
> -The servlet output is not JSON yet
> -Tags on rules would be nice to be able to run just the performance or
> security rules for example
> -A rule for checking OSGi configuration parameters would be useful.
> (*) credits to Joerg Hoh for that one, as well as inspiration in
> https://github.com/joerghoh/cq5-healthcheck
--
This message was sent by Atlassian JIRA
(v6.1#6144)
