# How to identify logstash pipeline status as complete?

**URL:** https://discuss.elastic.co/t/how-to-identify-logstash-pipeline-status-as-complete/140515
**Category:** Logstash
**Created:** [July 18, 2018, 10:46am UTC](https://discuss.elastic.co/t/how-to-identify-logstash-pipeline-status-as-complete/140515 "2018-07-18T10:46:34Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![abhisheksimion](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abhisheksimion/32/24623_2.png) [@abhisheksimion](https://discuss.elastic.co/u/abhisheksimion)
#### Post date: [July 18, 2018, 10:46am UTC](https://discuss.elastic.co/t/how-to-identify-logstash-pipeline-status-as-complete/140515/1 "2018-07-18T10:46:34Z")

</div>

I have below 2 queries

1. Is there a specific key in logstash API response which can identify that a pipeline (incremental) completed successfully? I checked [this](https://www.elastic.co/guide/en/logstash/6.x/node-stats-api.html) where the Pipeline stats give an event response `...in, filtered, out...` but did not find anything which can clearly say that a pipeline completed successfully.

2. In logstash logs for a particular run I get below result, what does `(seconds)` denote here?

`[2018-07-14T01:00:05,117][INFO][logstash.inputs.jdbc] (4.753178s) SELECT a.*,....`  
`[2018-07-14T02:00:45,221][INFO][logstash.inputs.jdbc] (42.543719s) SELECT pkey_ AS job_id,.....`

---

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [July 18, 2018, 8:23pm UTC](https://discuss.elastic.co/t/how-to-identify-logstash-pipeline-status-as-complete/140515/2 "2018-07-18T20:23:27Z")

</div>

Logstash doesn't have a concept of "done" or "complete".

---

<div class="post-metadata">

### Author: ![abhisheksimion](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abhisheksimion/32/24623_2.png) [@abhisheksimion](https://discuss.elastic.co/u/abhisheksimion)
#### Post date: [July 20, 2018, 5:26am UTC](https://discuss.elastic.co/t/how-to-identify-logstash-pipeline-status-as-complete/140515/3 "2018-07-20T05:26:28Z")

</div>

@magnusbaeck Thankyou for your reply, also what does the seconds denote after package information in logs? I see on schedule the executed query does not appear immediately, but takes time and differs on every schedule.

---

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [July 20, 2018, 6:39am UTC](https://discuss.elastic.co/t/how-to-identify-logstash-pipeline-status-as-complete/140515/4 "2018-07-20T06:39:53Z")

</div>

> Thankyou for your reply, also what does the seconds denote after package information in logs?

Unless it's the query execution time I don't know.

---

<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: [August 17, 2018, 6:39am UTC](https://discuss.elastic.co/t/how-to-identify-logstash-pipeline-status-as-complete/140515/5 "2018-08-17T06:39:53Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
