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

Chetan Mehrotra edited comment on SLING-4905 at 7/27/15 6:07 AM:
-----------------------------------------------------------------

Log panel now generates and supports links like

http://localhost:8080/system/console/slinglog/<appender name>?tail=<number of 
lines to dump>

Where
* Appender name - Names would be like _/logs/error.log_
* tail - Number of lines to include in dump. -1 to include whole file. Feature 
is based on SLING-4904

{noformat}
http://localhost:8080/system/console/slinglog/%2Flogs%2Ferror.log?tail=100
{noformat}

Implemented in http://svn.apache.org/r1692812


was (Author: chetanm):
Log panel now generates and supports links like

bq. http://localhost:8989/system/console/slinglog/<appender name>?tail=<number 
of lines to dump>

Where
* Appender name - Names would be like _/logs/error.log_
* tail - Number of lines to include in dump. -1 to include whole file. Feature 
is based on SLING-4904

{noformat}
http://localhost:8989/system/console/slinglog/%2Flogs%2Ferror.log?tail=100
{noformat}

Implemented in http://svn.apache.org/r1692812

> Log WebConsole Plugin should provide link to actual log file
> ------------------------------------------------------------
>
>                 Key: SLING-4905
>                 URL: https://issues.apache.org/jira/browse/SLING-4905
>             Project: Sling
>          Issue Type: New Feature
>          Components: Commons
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: Commons Log 4.0.4
>
>
> Currently the Sling Log Panel (Log component WebConsole Plugin) just provide 
> listing of active log files. There is a config printer which dumps content of 
> all active log file. It would be better if one can direct access log file 
> content of specific file. Also in doing that it should be possible to specify 
> how many line should be included



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to