Turn on logging in live production

Hi,
I was wondering about enabling logging for specific modules in ES. If I
wanted to turn on TRACE logging to see the merges, is it possible to turn
it on a live instance (without stopping ES, editing logging.yml and
restarting)?

Thanks,
Marie.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/82590d7a-2fc8-4b14-ad1f-d80799f77da7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

You can do so with the "logger" prefix in the cluster update settings api:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-update-settings.html#logger

You'll have to know the names of the loggers you want to change though.
You can figure that out by looking around the Elasticsearch code or by
finding examples.

Nik

On Thu, Oct 9, 2014 at 11:42 AM, Marie Jacob jacob.marie@gmail.com wrote:

Hi,
I was wondering about enabling logging for specific modules in ES. If I
wanted to turn on TRACE logging to see the merges, is it possible to turn
it on a live instance (without stopping ES, editing logging.yml and
restarting)?

Thanks,
Marie.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/82590d7a-2fc8-4b14-ad1f-d80799f77da7%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/82590d7a-2fc8-4b14-ad1f-d80799f77da7%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAPmjWd2Xk9JyqqCfob78HkCQM0q2A5U-ART%3DMfrEaDBTJ-0oVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Thanks!
So, would the call be something like this:

curl -XPUT localhost:9200/_cluster/settings -d '{ "persistent" : {
"logger.index.merge.scheduler" : "TRACE"} }'

On Thursday, October 9, 2014 11:51:59 AM UTC-4, Nikolas Everett wrote:

You can do so with the "logger" prefix in the cluster update settings api:

http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-update-settings.html#logger

You'll have to know the names of the loggers you want to change though.
You can figure that out by looking around the Elasticsearch code or by
finding examples.

Nik

On Thu, Oct 9, 2014 at 11:42 AM, Marie Jacob <jacob...@gmail.com
<javascript:>> wrote:

Hi,
I was wondering about enabling logging for specific modules in ES. If I
wanted to turn on TRACE logging to see the merges, is it possible to turn
it on a live instance (without stopping ES, editing logging.yml and
restarting)?

Thanks,
Marie.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/82590d7a-2fc8-4b14-ad1f-d80799f77da7%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/82590d7a-2fc8-4b14-ad1f-d80799f77da7%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d28637cb-b64c-4ceb-b8a2-6db4a2846d04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Yes. Something like that.
On Oct 9, 2014 6:17 PM, "Marie Jacob" jacob.marie@gmail.com wrote:

Thanks!
So, would the call be something like this:

curl -XPUT localhost:9200/_cluster/settings -d '{ "persistent" : {
"logger.index.merge.scheduler" : "TRACE"} }'

On Thursday, October 9, 2014 11:51:59 AM UTC-4, Nikolas Everett wrote:

You can do so with the "logger" prefix in the cluster update settings api:
http://www.elasticsearch.org/guide/en/elasticsearch/
reference/current/cluster-update-settings.html#logger

You'll have to know the names of the loggers you want to change though.
You can figure that out by looking around the Elasticsearch code or by
finding examples.

Nik

On Thu, Oct 9, 2014 at 11:42 AM, Marie Jacob jacob...@gmail.com wrote:

Hi,
I was wondering about enabling logging for specific modules in ES. If I
wanted to turn on TRACE logging to see the merges, is it possible to turn
it on a live instance (without stopping ES, editing logging.yml and
restarting)?

Thanks,
Marie.

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/82590d7a-2fc8-4b14-ad1f-d80799f77da7%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/82590d7a-2fc8-4b14-ad1f-d80799f77da7%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/d28637cb-b64c-4ceb-b8a2-6db4a2846d04%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/d28637cb-b64c-4ceb-b8a2-6db4a2846d04%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAPmjWd3ASNyxOo0wWoWw5h6iVfUSdcW%3DQHt3-dp3JmD5J4ruLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Hi Nikolas,

Is is possible to change log level to specific node ? This will be useful
incase of heavy indexing clusters.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/13b1f891-b442-4a38-920d-0201be2c8aee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Not without restarting it.
On Oct 10, 2014 7:13 AM, "Anantha Govindarajan" <
ananthagovindarajan@gmail.com> wrote:

Hi Nikolas,

Is is possible to change log level to specific node ? This will be useful
incase of heavy indexing clusters.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/13b1f891-b442-4a38-920d-0201be2c8aee%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/13b1f891-b442-4a38-920d-0201be2c8aee%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1-%2BtDPwuxyFTUzgTEgmKqwODsmbvYw8OCj7cLK%3DYniEQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Hi Nikolas,

Thanks for instant reply . will it be supported in coming releases ?

Since only few nodes are getting loaded in out es cluster , in that case i
need to watch logs on those nodes alone.

Also changing log level in entire cluster affects client node too .
Enabling TRACE level in client node(My application server) increases logs
size drastically .

So option to change log level in specific nodes will be definetly helpful
here.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/6f509298-7f95-4712-86e0-1e0f7c545d0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

I don't believe there are plans for changing logging level on a specific
node using the api. I'd file an issue with pretty much what you said.

You might be able to limit the verbosity by just setting TRACE or DEBUG on
the logger you need. Thats not as good as per node, but its something.

On Fri, Oct 10, 2014 at 7:33 AM, Anantha Govindarajan <
ananthagovindarajan@gmail.com> wrote:

Hi Nikolas,

Thanks for instant reply . will it be supported in coming releases ?

Since only few nodes are getting loaded in out es cluster , in that case i
need to watch logs on those nodes alone.

Also changing log level in entire cluster affects client node too .
Enabling TRACE level in client node(My application server) increases logs
size drastically .

So option to change log level in specific nodes will be definetly helpful
here.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/6f509298-7f95-4712-86e0-1e0f7c545d0a%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/6f509298-7f95-4712-86e0-1e0f7c545d0a%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0QsbFhWq9Zh3h68y_yyvXZVDEfMphPESJWNv3-8GHdVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.