I would not do this in Solr.
Post process the log file to split them out. That allows you to change the
definition of “slow” later, reprocess older files, etc.
Do log analysis with log analysis tools. Don’t try to push that too far up the
chain into the production server.
wunder
Walter Underwo
Indeed , the trouble hasn't got over yet.
So we got
https://issues.apache.org/jira/browse/SOLR-11453
created meantime.
I'll look forward to your updates.
Thanks again ,
Atita
On Thu, Oct 12, 2017 at 2:08 PM, Emir Arnautović <
emir.arnauto...@sematext.com> wrote:
> Hi Atita,
> I did not have ti
Hi Atita,
I did not have time to try it out, but will try to do it over the weekend if
you are still having troubles with it.
Regards,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/
> On 10 Oct 2017, at
No luck for me , did you give it a try meantime ?
M not sure , if I may have missed something , my logs are completely gone
after this change.
Wondering whats wrong with them.
-Atita
On Tue, Oct 10, 2017 at 5:58 PM, Atita Arora wrote:
> Sure thanks Emir,
> Let me give them a quick try and I'll
Sure thanks Emir,
Let me give them a quick try and I'll update you.
Thanks,
Atita
On Tue, Oct 10, 2017 at 5:28 PM, Emir Arnautović <
emir.arnauto...@sematext.com> wrote:
> Hi Atita,
> I did not try it, but I think that following could work:
>
>
> #logging queries
> log4j.logger.org.apache.solr.h
Hi Atita,
I did not try it, but I think that following could work:
#logging queries
log4j.logger.org.apache.solr.handler.component.QueryComponent=WARN,slow
log4j.appender.slow=org.apache.log4j.RollingFileAppender
log4j.appender.slow.File=${solr.log}/slow.log
log4j.appender.slow.layout=org.apach
Hi Emir,
So I made few changes to the log4j config , I am able to redirect these
logs to another file as well.
But as these are the WARN logs so I doubt any logs enabled at WARN level
are going to be redirected here in this new log file.
So precisely , I am using Solr 6.1 (in cloud mode) & I have
Hi Atita,
You should definetely go with log4j configuration as anything else would be
redoing what log4j can do. You already have slowQueryThresholdMillies to make
slow queries log with WARN and you can configure log4j to put such logs (class
+ level) to a separate file.
This seems like frequent
