Hi all,
meanwhile the Sling community gave their ok to proceed with the move the
health checks module to Felix [1]. I updated the patch for an initial
commit at [2] to also include the web console. At the moment it is
located
healthcheck/webconsoleplugin, but it can easily be moved to
webconsole-plugins if this is the preferred location (most plugins are
there, but there are some exceptions like ipojo/webconsole-plugin. In
a way I like it better to have it all bundled under one directory
"healthcheck".
So as far as I can tell, I think everything would be ready for the
initial
commit of the attached patch.
Best Regards
Georg
[1]
http://apache-sling.73963.n3.nabble.com/hackathon-health-checks-tp4086283p4087711.html
[2]
https://issues.apache.org/jira/browse/FELIX-5952?focusedCommentId=16675773&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16675773
On 2018-10-12 11:39, Andrei Dulvac wrote:
+1
I think it's best we have the HCs in Felix and work on a merge of HCs
and
systemready.
- Andrei
On Fri, Oct 12, 2018 at 11:34 AM Carsten Ziegeler
<[email protected]>
wrote:
As there is a lot of overlap and an indication from all sides to work
together on a single solution, +1 for working on this solution in the
Apache Felix project.
Regards
Carsten
Am 11.10.2018 um 09:41 schrieb Christian Schneider:
> 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
>
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
