[
https://issues.apache.org/jira/browse/SOLR-14310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056517#comment-17056517
]
Jan Høydahl commented on SOLR-14310:
------------------------------------
I agree that anything but simple show last-N lines is overkill. Did you plan to
serve this from the actual file system or from some memory buffer? Remember
that for some deployments like containers, Solr may very well log to stdout and
not store any log files on disk locally.
> Expose solr logs with basic filters via HTTP
> --------------------------------------------
>
> Key: SOLR-14310
> URL: https://issues.apache.org/jira/browse/SOLR-14310
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Priority: Major
>
> path {{/api/node/tools/logs}}
> params
> * lines : (default 100) no:of lines to be shown. the most recent lines are
> shown
> * collection : (multivalued) filter log lines by collections
> * shard : (multivalued) filter log lines by shard name
> * core: (multivalued)filter log lines by cores
> * startTime: timestamp start
> * endTime: Timestamp end
> * className :(multivalued) Name of the class in logs
> * logLevel: (multivalued) . INFO/DEBUG etc
> * threadNamePrefix: (multivalued) : eg: qtp ,searchExecutor ,
> solrHandlerExecutor etc
> The output will be in plain text format
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
