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

ASF subversion and git services commented on SOLR-14558:
--------------------------------------------------------

Commit a7792b129b096245d70ab960f57d15842c60bbd6 in lucene-solr's branch 
refs/heads/master from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=a7792b1 ]

SOLR-14558: Record all log lines in SolrLogPostTool (#1570)



> SolrLogPostTool should record all lines
> ---------------------------------------
>
>                 Key: SOLR-14558
>                 URL: https://issues.apache.org/jira/browse/SOLR-14558
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: scripts and tools
>    Affects Versions: master (9.0)
>            Reporter: Jason Gerlowski
>            Assignee: Jason Gerlowski
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, SolrLogPostTool recognizes a predefined set of "types" of log 
> messages: queries, errors, commits, etc.  This makes it easy to find and 
> explore the traffic your cluster is seeing.
> But it would also be cool if we also indexed all records, even if many of 
> them are just assigned a catch-all "other" type_s value.  We won't be able to 
> parse out detailed values from the log messages the way we would for 
> type_s=query for example, but we can still store the line and timestamp.  
> Gives much better search over the logs than dropping down to "grep" for 
> anything that's not one of the predefined types.
>  



--
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

Reply via email to