[jira] [Updated] (SOLR-12344) SolrSlf4jReporter doesn't set MDC context
[
https://issues.apache.org/jira/browse/SOLR-12344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated SOLR-12344:
-
Fix Version/s: 7.5
> SolrSlf4jReporter doesn't set MDC context
> -
>
> Key: SOLR-12344
> URL: https://issues.apache.org/jira/browse/SOLR-12344
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: metrics
>Reporter: Varun Thacker
>Assignee: Andrzej Bialecki
>Priority: Major
> Fix For: 7.5
>
> Attachments: SOLR-12344.patch
>
>
> I setup a slf4j reporter like this on master
> solr.xml
> {code:java}
>
>class="org.apache.solr.metrics.reporters.SolrSlf4jReporter">
> 1
> UPDATE./update.requestTimes
> update_logger
>
> {code}
> log4j2.xml
> {code:java}
>
>
>
>
>
>
>
> %-4r [%t] %-5p %c %x [%X{collection} %X{shard} %X{replica}
> %X{core}] %c; %m%n
>
>
>
> name="RollingFile"
> fileName="${sys:solr.log.dir}/solr.log"
> filePattern="${sys:solr.log.dir}/solr.log.%i" >
>
>
> %-5p - %d{-MM-dd HH:mm:ss.SSS}; [%X{collection} %X{shard}
> %X{replica} %X{core}] %c; %m%n
>
>
>
>
>
>
>
>
> name="RollingMetricFile"
> fileName="${sys:solr.log.dir}/solr_metric.log"
> filePattern="${sys:solr.log.dir}/solr_metric.log.%i" >
>
>
> %-5p - %d{-MM-dd HH:mm:ss.SSS}; [%X{collection} %X{shard}
> %X{replica} %X{core}] %c; %m%n
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> The output I get from the solr_metric.log file is like this
> {code:java}
> INFO - 2018-05-11 15:31:16.009; [ ] update_logger; type=TIMER,
> name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
> stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
> mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
> duration_unit=milliseconds
> INFO - 2018-05-11 15:31:17.010; [ ] update_logger; type=TIMER,
> name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
> stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
> mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
> duration_unit=milliseconds
> INFO - 2018-05-11 15:31:18.010; [ ] update_logger; type=TIMER,
> name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
> stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
> mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
> duration_unit=milliseconds{code}
> On a JVM which has multiple cores, this will become impossible to tell where
> it's coming from if MDC context is not set
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-12344) SolrSlf4jReporter doesn't set MDC context
[
https://issues.apache.org/jira/browse/SOLR-12344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated SOLR-12344:
-
Attachment: SOLR-12344.patch
> SolrSlf4jReporter doesn't set MDC context
> -
>
> Key: SOLR-12344
> URL: https://issues.apache.org/jira/browse/SOLR-12344
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: metrics
>Reporter: Varun Thacker
>Assignee: Andrzej Bialecki
>Priority: Major
> Attachments: SOLR-12344.patch
>
>
> I setup a slf4j reporter like this on master
> solr.xml
> {code:java}
>
>class="org.apache.solr.metrics.reporters.SolrSlf4jReporter">
> 1
> UPDATE./update.requestTimes
> update_logger
>
> {code}
> log4j2.xml
> {code:java}
>
>
>
>
>
>
>
> %-4r [%t] %-5p %c %x [%X{collection} %X{shard} %X{replica}
> %X{core}] %c; %m%n
>
>
>
> name="RollingFile"
> fileName="${sys:solr.log.dir}/solr.log"
> filePattern="${sys:solr.log.dir}/solr.log.%i" >
>
>
> %-5p - %d{-MM-dd HH:mm:ss.SSS}; [%X{collection} %X{shard}
> %X{replica} %X{core}] %c; %m%n
>
>
>
>
>
>
>
>
> name="RollingMetricFile"
> fileName="${sys:solr.log.dir}/solr_metric.log"
> filePattern="${sys:solr.log.dir}/solr_metric.log.%i" >
>
>
> %-5p - %d{-MM-dd HH:mm:ss.SSS}; [%X{collection} %X{shard}
> %X{replica} %X{core}] %c; %m%n
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> The output I get from the solr_metric.log file is like this
> {code:java}
> INFO - 2018-05-11 15:31:16.009; [ ] update_logger; type=TIMER,
> name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
> stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
> mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
> duration_unit=milliseconds
> INFO - 2018-05-11 15:31:17.010; [ ] update_logger; type=TIMER,
> name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
> stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
> mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
> duration_unit=milliseconds
> INFO - 2018-05-11 15:31:18.010; [ ] update_logger; type=TIMER,
> name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
> stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
> mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
> duration_unit=milliseconds{code}
> On a JVM which has multiple cores, this will become impossible to tell where
> it's coming from if MDC context is not set
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-12344) SolrSlf4jReporter doesn't set MDC context
[
https://issues.apache.org/jira/browse/SOLR-12344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett updated SOLR-12344:
-
Component/s: metrics
> SolrSlf4jReporter doesn't set MDC context
> -
>
> Key: SOLR-12344
> URL: https://issues.apache.org/jira/browse/SOLR-12344
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: metrics
>Reporter: Varun Thacker
>Priority: Major
>
> I setup a slf4j reporter like this on master
> solr.xml
> {code:java}
>
>class="org.apache.solr.metrics.reporters.SolrSlf4jReporter">
> 1
> UPDATE./update.requestTimes
> update_logger
>
> {code}
> log4j2.xml
> {code:java}
>
>
>
>
>
>
>
> %-4r [%t] %-5p %c %x [%X{collection} %X{shard} %X{replica}
> %X{core}] %c; %m%n
>
>
>
> name="RollingFile"
> fileName="${sys:solr.log.dir}/solr.log"
> filePattern="${sys:solr.log.dir}/solr.log.%i" >
>
>
> %-5p - %d{-MM-dd HH:mm:ss.SSS}; [%X{collection} %X{shard}
> %X{replica} %X{core}] %c; %m%n
>
>
>
>
>
>
>
>
> name="RollingMetricFile"
> fileName="${sys:solr.log.dir}/solr_metric.log"
> filePattern="${sys:solr.log.dir}/solr_metric.log.%i" >
>
>
> %-5p - %d{-MM-dd HH:mm:ss.SSS}; [%X{collection} %X{shard}
> %X{replica} %X{core}] %c; %m%n
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> The output I get from the solr_metric.log file is like this
> {code:java}
> INFO - 2018-05-11 15:31:16.009; [ ] update_logger; type=TIMER,
> name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
> stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
> mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
> duration_unit=milliseconds
> INFO - 2018-05-11 15:31:17.010; [ ] update_logger; type=TIMER,
> name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
> stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
> mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
> duration_unit=milliseconds
> INFO - 2018-05-11 15:31:18.010; [ ] update_logger; type=TIMER,
> name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
> stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
> mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
> duration_unit=milliseconds{code}
> On a JVM which has multiple cores, this will become impossible to tell where
> it's coming from if MDC context is not set
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-12344) SolrSlf4jReporter doesn't set MDC context
[
https://issues.apache.org/jira/browse/SOLR-12344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker updated SOLR-12344:
-
Description:
I setup a slf4j reporter like this on master
solr.xml
{code:java}
1
UPDATE./update.requestTimes
update_logger
{code}
log4j2.xml
{code:java}
%-4r [%t] %-5p %c %x [%X{collection} %X{shard} %X{replica} %X{core}]
%c; %m%n
%-5p - %d{-MM-dd HH:mm:ss.SSS}; [%X{collection} %X{shard}
%X{replica} %X{core}] %c; %m%n
%-5p - %d{-MM-dd HH:mm:ss.SSS}; [%X{collection} %X{shard}
%X{replica} %X{core}] %c; %m%n
{code}
The output I get from the solr_metric.log file is like this
{code:java}
INFO - 2018-05-11 15:31:16.009; [ ] update_logger; type=TIMER,
name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
duration_unit=milliseconds
INFO - 2018-05-11 15:31:17.010; [ ] update_logger; type=TIMER,
name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
duration_unit=milliseconds
INFO - 2018-05-11 15:31:18.010; [ ] update_logger; type=TIMER,
name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
duration_unit=milliseconds{code}
On a JVM which has multiple cores, this will become impossible to tell where
it's coming from if MDC context is not set
was:
I setup a slf4j reporter like this on mater
solr.xml
{code:java}
1
UPDATE./update.requestTimes
update_logger
{code}
log4j2.xml
{code:java}
%-4r [%t] %-5p %c %x [%X{collection} %X{shard} %X{replica} %X{core}]
%c; %m%n
%-5p - %d{-MM-dd HH:mm:ss.SSS}; [%X{collection} %X{shard}
%X{replica} %X{core}] %c; %m%n
%-5p - %d{-MM-dd HH:mm:ss.SSS}; [%X{collection} %X{shard}
%X{replica} %X{core}] %c; %m%n
{code}
The output I get from the solr_metric.log file is like this
{code:java}
INFO - 2018-05-11 15:31:16.009; [ ] update_logger; type=TIMER,
name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
duration_unit=milliseconds
INFO - 2018-05-11 15:31:17.010; [ ] update_logger; type=TIMER,
name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
duration_unit=milliseconds
INFO - 2018-05-11 15:31:18.010; [ ] update_logger; type=TIMER,
name=UPDATE./update.requestTimes, count=0, min=0.0, max=0.0, mean=0.0,
stddev=0.0, median=0.0, p75=0.0, p95=0.0, p98=0.0, p99=0.0, p999=0.0,
mean_rate=0.0, m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second,
duration_unit=milliseconds{code}
On a JVM which has multiple cores, this will become impossible to tell where
it's coming from if MDC context is not set
> SolrSlf4jReporter doesn't set MDC context
> -
>
> Key: SOLR-12344
> URL: https://issues.apache.org/jira/browse/SOLR-12344
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Varun Thacker
>Priority: Major
>
> I setup a slf4j reporter like this on master
> solr.xml
> {code:java}
>
>class="org.apache.solr.metrics.reporters.SolrSlf4jReporter">
> 1
> UPDATE./update.requestTimes
> update_logger
>
> {code}
> log4j2.xml
> {code:java}
>
>
>
>
>
>
>
> %-4r [%t] %-5p %c %x [%X{collection} %X{shard} %X{replica}
> %X{core}] %c; %m%n
>
>
>
> name="RollingFile"
> fileName="${sys:solr.log.dir}/solr.log"
> filePattern="${sys:solr.log.dir}/solr.log.%i" >
>
>
> %-5p - %d{-MM-dd HH:mm:ss.SSS}; [%X{collection} %X{shard}
> %X{replica} %X{core}] %c;
