[ 
https://issues.apache.org/jira/browse/SLING-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002217#comment-16002217
 ] 

Georg Henzler edited comment on SLING-6834 at 5/9/17 7:33 AM:
--------------------------------------------------------------

Having the space in the RegEx was a bug - the documentation (both the html 
rendering of the HC servlet and the webconsole) state that the hc tags have to 
be provided comma-separated (hence the {{;}} should be removed as well). In the 
web console currently only {{,}} is supported as delimiter (web console inputs 
are split at a different code position).


was (Author: henzlerg):
Having the space in the RegEx was a bug - the documentation (both the html 
rendering of the HC servlet and the webconsole) state that the hc tags have to 
be provided comma-separated (hence the {{;}} should be removed as well)

> Introduce a new, verbose and text-based output format that can be used for 
> console based applications
> -----------------------------------------------------------------------------------------------------
>
>                 Key: SLING-6834
>                 URL: https://issues.apache.org/jira/browse/SLING-6834
>             Project: Sling
>          Issue Type: New Feature
>          Components: Health Check
>    Affects Versions: Health Check Core 1.2.6
>            Reporter: Georg Henzler
>            Assignee: Georg Henzler
>             Fix For: Health Check Core 1.2.8
>
>
> For both Jenkins pipelines and Docker container setups it would be nice to 
> have a simple text based response format that can be printed to the log (to 
> have them include more verbose information). 
> The existing formats html and json are not very readable in a log file, the 
> existing format txt is only printing OK, WARN or CRITICAL (minimised response 
> entity optimised for load balancer usage). 
> I would propose to add a new format {{.verbose.txt}} (was intially 
> {{exttxt}}). 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to