[
https://issues.apache.org/jira/browse/SOLR-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254390#comment-13254390
]
Ryan McKinley commented on SOLR-3358:
-------------------------------------
After thinking a bit more on this, I think we can (optionally) take it another
step forward. The log appender/handler could actually send the event to a solr
index. Then we could support more complex search/filtering directly with solr.
As a first step, I'll replace my custom format with a SolrDocumentList so that
anything we do for the in-memory solution could be reused for an index based
solution.
In a cloud/distributed environment, if all the instances log to the same server
it would be much easier to spot problems across the whole system.
I'll work up a patch
bq. Right now, i was not able to produce one entry which contains a
trace-element
try:
http://localhost:8983/solr/admin/logging?since=0&test=true
this will add a message (and exception) at each level
> Show Logging Events in Admin UI
> -------------------------------
>
> Key: SOLR-3358
> URL: https://issues.apache.org/jira/browse/SOLR-3358
> Project: Solr
> Issue Type: Bug
> Components: web gui
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Attachments: SOLR-3358-logging.patch
>
>
> The UI should be able to show the last few log messages. To support this, we
> will need to register an Appender (log4j) or Handler
> (JUL) and keep a buffer of recent log events.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
