# Logstash Flush Logs Explanation

**URL:** https://discuss.elastic.co/t/logstash-flush-logs-explanation/62751
**Category:** Logstash
**Created:** [October 11, 2016, 7:53pm UTC](https://discuss.elastic.co/t/logstash-flush-logs-explanation/62751 "2016-10-11T19:53:46Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![chromechris](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@chromechris](https://discuss.elastic.co/u/chromechris)
#### Post date: [October 11, 2016, 7:53pm UTC](https://discuss.elastic.co/t/logstash-flush-logs-explanation/62751/1 "2016-10-11T19:53:46Z")

</div>

Hello Loggers,

I was wondering if someone could explain what the logs produced by logstash in "logstash.log" mean when you restart Logstash and there is an event flush after sending the SIGTERM to Logstash. Sample Log:

index=\>"indexname-%{+[YYYY.MM](http://YYYY.MM)}", user=\>"username", password=\>, ssl=\>true, cacert=\>"/opt/logstash/some-file.pem", codec=\>\<LogStash::Codecs::Plain charset=\>"UTF-8"\>, workers=\>1, manage\_template=\>true, templat  
e\_name=\>"logstash", template\_overwrite=\>false, flush\_size=\>500, idle\_flush\_time=\>1, doc\_as\_upsert=\>false, max\_retries=\>3, script\_type=\>"inline", script\_var\_name=\>"event", scripted\_upsert=\>false, retry\_max\_interval=\>2, retry\_max\_items=\>500, retry\_on\_conflict=\>1, action=\>"i  
ndex", ssl\_certificate\_verification=\>true, sniffing=\>false, sniffing\_delay=\>5, discovery=\>"zen", aws\_protocol=\>"https"\>]\>, :busy\_workers=\>0}, {:type=\>"elasticsearch", :config=\>{"hosts"=\>["[hostname.com:9224](http://hostname.com:9224)", "[hostname.com:9224](http://hostname.com:9224)", "[hostname.com:9224](http://hostname.com:9224)"]

What do the following terms mean:  
workers: (I believe the worker takes in multiple events from the input threads, then runs all these events as a batch to the Filter/Output)  
manage\_template: (I though the templates only belong to ES [Elasticsearch])  
template\_name:  
template\_overwrite:  
flush\_size: (Flush size in what units/metrics?)  
idle\_flush\_time:  
doc\_as\_upsert:  
max\_retries:  
script\_type:  
script\_var\_name:  
scripted\_upsert:  
retry\_max\_interval:  
retry\_max\_items:  
retry\_on\_conflict:  
sniffing\_delay:  
discovery:  
busy\_workers:

Thanks In Advance,

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [October 12, 2016, 4:29am UTC](https://discuss.elastic.co/t/logstash-flush-logs-explanation/62751/2 "2016-10-12T04:29:39Z")

</div>

You probably want to start here - [https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html)

---

<div class="post-metadata">

### Author: ![chromechris](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@chromechris](https://discuss.elastic.co/u/chromechris)
#### Post date: [October 12, 2016, 3:47pm UTC](https://discuss.elastic.co/t/logstash-flush-logs-explanation/62751/3 "2016-10-12T15:47:35Z")

</div>

Thanks!

---

<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:34am UTC](https://discuss.elastic.co/t/logstash-flush-logs-explanation/62751/4 "2017-07-06T04:34:32Z")

</div>