# Logging Question

**URL:** <https://discuss.elastic.co/t/logging-question/5465>\
**Category:** Elasticsearch\
**Created:** [September 27, 2011, 5:28pm UTC](https://discuss.elastic.co/t/logging-question/5465 "2011-09-27T17:28:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Neil1](https://avatars.discourse-cdn.com/v4/letter/n/278dde/32.png) [@Neil1](https://discuss.elastic.co/u/Neil1)\
**Post date:** [September 27, 2011, 5:28pm UTC](https://discuss.elastic.co/t/logging-question/5465/1 "2011-09-27T17:28:33Z")

</div>

Hi,

Thanks for the previous help.

I have a couple more questions. Is there any way to log the actual  
calls any client makes to the elastic search server?

Right now I'd like to log the put operations on the elastic search  
side and I have everything set to TRACE and I'm not seeing anything in  
my logs.

Neil

rootLogger: TRACE, console, file  
logger:

# log action execution errors for easier debugging

action: TRACE

# reduce the logging for aws, too much is logged under the default

INFO  
com.amazonaws: TRACE

# gateway

#gateway: TRACE  
index.gateway: TRACE

# peer shard recovery

index.shard.recovery: TRACE

# discovery

discovery: TRACE

appender:  
console:  
type: console  
layout:  
type: consolePattern  
conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n"

file:  
type: dailyRollingFile  
file: ${path.logs}/${cluster.name}.log  
datePattern: "'.'yyyy-MM-dd"  
layout:  
type: pattern  
conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n"

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [September 27, 2011, 9:20pm UTC](https://discuss.elastic.co/t/logging-question/5465/2 "2011-09-27T21:20:12Z")

</div>

Action level requests (or REST wrappers around it) are not logged, not on  
trace level as well. Why do you need it?

On Tue, Sep 27, 2011 at 8:28 PM, Neil [neilmatthewlott@gmail.com](mailto:neilmatthewlott@gmail.com) wrote:

> Hi,
> 
> Thanks for the previous help.
> 
> I have a couple more questions. Is there any way to log the actual  
> calls any client makes to the Elasticsearch server?
> 
> Right now I'd like to log the put operations on the Elasticsearch  
> side and I have everything set to TRACE and I'm not seeing anything in  
> my logs.
> 
> Neil
> 
> rootLogger: TRACE, console, file  
> logger:
> 
> # log action execution errors for easier debugging
> 
> action: TRACE
> 
> # reduce the logging for aws, too much is logged under the default
> 
> INFO  
> com.amazonaws: TRACE
> 
> # gateway
> 
> #gateway: TRACE  
> index.gateway: TRACE
> 
> # peer shard recovery
> 
> index.shard.recovery: TRACE
> 
> # discovery
> 
> discovery: TRACE
> 
> appender:  
> console:  
> type: console  
> layout:  
> type: consolePattern  
> conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n"
> 
> file:  
> type: dailyRollingFile  
> file: ${path.logs}/${cluster.name}.log  
> datePattern: "'.'yyyy-MM-dd"  
> layout:  
> type: pattern  
> conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n"

---

<div class="post-metadata">

**Author:** ![Neil1](https://avatars.discourse-cdn.com/v4/letter/n/278dde/32.png) [@Neil1](https://discuss.elastic.co/u/Neil1)\
**Post date:** [September 28, 2011, 3:09am UTC](https://discuss.elastic.co/t/logging-question/5465/3 "2011-09-28T03:09:50Z")

</div>

As a way to audit what's going on. A lot of time a support issue  
comes in and I need to be able to trace  
everything to verify the problem lies.

---

<div class="post-metadata">

**Author:** ![Paul\_Smith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paul_smith/32/1323_2.png) [@Paul\_Smith](https://discuss.elastic.co/u/Paul_Smith)\
**Post date:** [September 30, 2011, 5:49am UTC](https://discuss.elastic.co/t/logging-question/5465/4 "2011-09-30T05:49:42Z")

</div>

I personally would like the ability to log TRACE level incoming requests,  
it's handy when you're using, say, the Java API and wondering why something  
is not working, to see the raw JSON being sent can be useful.

slightly different, but it would be good to be able to log things like  
Apache access log style so that one could replay a clusters logs against a  
test cluster for instance when testing new setups, configs etc for  
performance.

On 28 September 2011 13:09, Neil [neilmatthewlott@gmail.com](mailto:neilmatthewlott@gmail.com) wrote:

> As a way to audit what's going on. A lot of time a support issue  
> comes in and I need to be able to trace  
> everything to verify the problem lies.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:53am UTC](https://discuss.elastic.co/t/logging-question/5465/5 "2017-07-06T03:53:17Z")

</div>