# Increase/improve logging to debug slowdowns?

**URL:** <https://discuss.elastic.co/t/increase-improve-logging-to-debug-slowdowns/4053>\
**Category:** Elasticsearch\
**Created:** [March 7, 2011, 11:39pm UTC](https://discuss.elastic.co/t/increase-improve-logging-to-debug-slowdowns/4053 "2011-03-07T23:39:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Taylor](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@David\_Taylor](https://discuss.elastic.co/u/David_Taylor)\
**Post date:** [March 7, 2011, 11:39pm UTC](https://discuss.elastic.co/t/increase-improve-logging-to-debug-slowdowns/4053/1 "2011-03-07T23:39:16Z")

</div>

I'm trying to track down delays we're seeing in our application. Our  
monitoring indicates the application is _sometimes_ held up for long periods  
of time while talking to elasticsearch.

Can someone recommend logging settings that would help me get to the bottom  
of what elasticsearch is doing at any given time?

I guess, at a minimum, I should be logging when elasticsearch is merging and  
expunging? We currently have the following in logging.yml (which I thought  
would do what I want):

```
rootLogger: INFO, console, file
logger:
  action: DEBUG
  com.amazonaws: WARN

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"

```

Any suggestions appreciated. Thanks.

Cheers,  
David.

---

<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:** [March 8, 2011, 6:04am UTC](https://discuss.elastic.co/t/increase-improve-logging-to-debug-slowdowns/4053/2 "2011-03-08T06:04:12Z")

</div>

There isn't logging that one can enabled for merging operations. In master, there are stats on merging happening though.

The two places that you would want to start with checking is long garbage collection and merging. Another one is to make sure elasticsearch has enough memory (check the node stats for field data cache evictions and how much memory it takes, as well as the filter cache.

-shay.banon  
On Tuesday, March 8, 2011 at 1:39 AM, David Taylor wrote:

> I'm trying to track down delays we're seeing in our application. Our monitoring indicates the application is _sometimes_ held up for long periods of time while talking to elasticsearch.
> 
> Can someone recommend logging settings that would help me get to the bottom of what elasticsearch is doing at any given time?
> 
> I guess, at a minimum, I should be logging when elasticsearch is merging and expunging? We currently have the following in logging.yml (which I thought would do what I want):
> 
> rootLogger: INFO, console, file  
> logger:  
> action: DEBUG  
> com.amazonaws: WARN
> 
> 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"
> 
> Any suggestions appreciated. Thanks.
> 
> Cheers,  
> David.

---

<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, 4:10am UTC](https://discuss.elastic.co/t/increase-improve-logging-to-debug-slowdowns/4053/3 "2017-07-06T04:10:37Z")

</div>

Closed on July 6, 2017, 4:10am UTC