Sling health checks (hc) provide a framework to continually check the
system health of an OSGi system.
The result of the individual checks is grouped by labels and can be
retrieved using JMX and a servlet.
( https://github.com/apache?utf8=%E2%9C%93&q=sling-hc&type=&language= )

The sling community discussed to offer to move this project to felix. (
https://lists.apache.org/thread.html/d42c2064bf98d10b4f9b5d424384e2e83993e41613e643de944c7c35@%3Cdev.sling.apache.org%3E
)
By having sling hc in felix I hope this framework can reach a larger
audience than in sling.
Georg Henzler took care of changing the package names and removing
dependencies from other sling modules. He provided a zip file with a
possible initial contribution in this issue:
https://issues.apache.org/jira/browse/FELIX-5952

There is quite some overlap with felix system ready. So if we accept the
offer then we also have to look into merging the two frameworks. I think at
least for long term we should not keep both. As far as I learned the Sling
HC API can cover most of the features of the systemready framework api. As
sling hc is a lot more mature and battle proven I can imagine to move to
this basic framework and change the system ready checks to this API.

So what do you think?

Christian

-- 
-- 
Christian Schneider
http://www.liquid-reality.de

Computer Scientist
http://www.adobe.com

Reply via email to