Logging Question


(Neil) #1

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"


(Shay Banon) #2

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 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 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"


(Neil) #3

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.


(Paul Smith) #4

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 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.


(system) #5