# Logstash Events Stats API

**URL:** <https://discuss.elastic.co/t/logstash-events-stats-api/239212>\
**Category:** Logstash\
**Created:** [June 30, 2020, 2:12am UTC](https://discuss.elastic.co/t/logstash-events-stats-api/239212 "2020-06-30T02:12:20Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rahul\_Kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rahul_kumar4/32/67369_2.png) [@Rahul\_Kumar4](https://discuss.elastic.co/u/Rahul_Kumar4)\
**Post date:** [June 30, 2020, 2:12am UTC](https://discuss.elastic.co/t/logstash-events-stats-api/239212/1 "2020-06-30T02:12:20Z")

</div>

What do the fields `duration_in_millis` and `queue_push_duration_in_millis` in Logstash's Events Stats API response in the link below mean?

[https://www.elastic.co/guide/en/logstash/current/node-stats-api.html#event-stats](https://www.elastic.co/guide/en/logstash/current/node-stats-api.html#event-stats)

---

<div class="post-metadata">

**Author:** ![Rahul\_Kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rahul_kumar4/32/67369_2.png) [@Rahul\_Kumar4](https://discuss.elastic.co/u/Rahul_Kumar4)\
**Post date:** [June 30, 2020, 2:15am UTC](https://discuss.elastic.co/t/logstash-events-stats-api/239212/2 "2020-06-30T02:15:02Z")

</div>

And related to the question above - for what duration are the fields `in` and `out` aggregated for by default - `last 1 hour`, `last 24 hours`, `last 7 days` ? and can that default be altered?

---

<div class="post-metadata">

**Author:** ![Rahul\_Kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rahul_kumar4/32/67369_2.png) [@Rahul\_Kumar4](https://discuss.elastic.co/u/Rahul_Kumar4)\
**Post date:** [July 7, 2020, 12:23am UTC](https://discuss.elastic.co/t/logstash-events-stats-api/239212/3 "2020-07-07T00:23:10Z")

</div>

Bumping up!

---

<div class="post-metadata">

**Author:** ![Rahul\_Kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rahul_kumar4/32/67369_2.png) [@Rahul\_Kumar4](https://discuss.elastic.co/u/Rahul_Kumar4)\
**Post date:** [July 7, 2020, 12:23am UTC](https://discuss.elastic.co/t/logstash-events-stats-api/239212/4 "2020-07-07T00:23:30Z")

</div>

Anyone here?

---

<div class="post-metadata">

**Author:** ![kernelpanic](https://avatars.discourse-cdn.com/v4/letter/k/c89c15/32.png) [@kernelpanic](https://discuss.elastic.co/u/kernelpanic)\
**Post date:** [July 7, 2020, 9:57am UTC](https://discuss.elastic.co/t/logstash-events-stats-api/239212/5 "2020-07-07T09:57:07Z")

</div>

These two links might help:

> **[Monitoring Logstash Filters: X-ray glasses included](https://www.elastic.co/blog/monitoring-logstash-filters)**

> [@\_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):
>
> We recently upgraded Logstash to 5.4.1 and have been having some performance issues. In order to try drilling down into what is going on I have been drilling into the [node stats API](https://www.elastic.co/guide/en/logstash/current/node-stats-api.html). However not all of the fields are well documented. In the results there is a duration\_in\_millis field and a queue\_push\_duration\_in\_millis field. "pipeline" : { "events" : { "duration\_in\_millis" : 3766620, "in" : 489102, "filtered" : 489088, "out" : 485088, "queue\_push\_duration\_i…

---

<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 4, 2020, 9:57am UTC](https://discuss.elastic.co/t/logstash-events-stats-api/239212/6 "2020-08-04T09:57:09Z")

</div>

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