# Timing Questions with Logstash pipelines v. API Data
**URL:** https://discuss.elastic.co/t/timing-questions-with-logstash-pipelines-v-api-data/321235
**Category:** Logstash
**Tags:** ingest-pipeline
**Created:** [December 14, 2022, 6:46pm UTC](https://discuss.elastic.co/t/timing-questions-with-logstash-pipelines-v-api-data/321235 "2022-12-14T18:46:27Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Broken08](https://discuss.elastic.co/u/Broken08)
#### Post date: [December 14, 2022, 6:46pm UTC](https://discuss.elastic.co/t/timing-questions-with-logstash-pipelines-v-api-data/321235/1 "2022-12-14T18:46:27Z")
I have 9 logstash Pipelines that run to ingest data into ES.
I was trying to do some math initially by taking the time the pipeline starts ingest (Looking at the \*.pipeline.log file looking at the time the query started and comparing it to the last document that was written into ES.
When we do that, we see about 3 - 5 minutes (assuming the network has some latency and other stuff going on). BUT when I look at the pipeline in the API i.e.
/stats/pipelines/PIPELINE\_NAME?pretty and I see a duration\_in\_millis of like 7 seconds Which doesnt really line up.
So, what is the realistic way of calculating runtime of pipeline and validation that everything sent is ingested so I can report a complete time?
I did see this ([\_node/stats - duration\_in\_millis vs queue\_push\_duration\_in\_millis](https://discuss.elastic.co/t/-node-stats-duration-in-millis-vs-queue-push-duration-in-millis/90000)) which has some great info but doesnt really answer my question.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 11, 2023, 6:46pm UTC](https://discuss.elastic.co/t/timing-questions-with-logstash-pipelines-v-api-data/321235/2 "2023-01-11T18:46:51Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.