[
https://issues.apache.org/jira/browse/SLING-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14618301#comment-14618301
]
Georg Henzler commented on SLING-4862:
--------------------------------------
I discussed this with [~jhoh] some time ago - this could be a Sling servlet
that takes the tag config from the resource (allowing multiple to have multiple
configs as resources at different URLs) or a low-level whiteboard servlet (just
using request parameters for tags and response format). The advantage from the
latter is performance (no jcr access, it's circumventing sling resource
mapping/authentication) and reliability (less dependencies, even if sling was
completely broken it can still answer as it relies solely on OSGi). The missing
authentication is normally not a problem if a path at under /system is used
(e.g /system/health) as those paths are normally hidden from the internet (but
I would use configuration policy required for the servlet to only activate if
desired).
[~bdelacretaz] we have been using a servlet as described above for quite a
while already, should we contribute it or would you like to use a different
approach?
> Sling Health Checks Servlet
> ---------------------------
>
> Key: SLING-4862
> URL: https://issues.apache.org/jira/browse/SLING-4862
> Project: Sling
> Issue Type: Improvement
> Components: Health Check
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> A Servlet that can execute health checks would be useful.
> It can take as input the tags of the HCs to execute, and output their results
> in JSON format.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
