# Duration\_in\_millis shows too high values

**URL:** https://discuss.elastic.co/t/duration-in-millis-shows-too-high-values/108563
**Category:** Logstash
**Created:** [November 21, 2017, 1:03pm UTC](https://discuss.elastic.co/t/duration-in-millis-shows-too-high-values/108563 "2017-11-21T13:03:31Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![mathias](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mathias/32/23176_2.png) [@mathias](https://discuss.elastic.co/u/mathias)
#### Post date: [November 21, 2017, 1:03pm UTC](https://discuss.elastic.co/t/duration-in-millis-shows-too-high-values/108563/1 "2017-11-21T13:03:32Z")

</div>

Hi,

I am using ELK 5.6.3

I am looking at the delay of events and I can't understand the output values.

```
curl -s logstash:9600/_node/stats/pipeline | jq .pipeline.plugins.outputs
[
  {
    "id": "events_output_to_elasticsearch",
    "events": {
      "duration_in_millis": 29552,
      "in": 4512,
      "out": 4512
    },
    "name": "elasticsearch"
  },
  {
    "id": "beats_output_to_elasticsearch",
    "events": {
      "duration_in_millis": 18428,
      "in": 20251,
      "out": 20251
    },
    "name": "elasticsearch"
  }
]

```

The input delay is just 86 ms.

```
curl -s logstash:9600/_node/stats/pipeline | jq .pipeline.plugins.inputs[1]
{
  "id": "tcp_input_port_4029_eventdecoder",
  "events": {
    "out": 4979,
    "queue_push_duration_in_millis": 86
  },
  "name": "tcp"
}

```

For the events\_output is is 29 seconds.  
When I hit the button to generate an event it takes approximately 2 seconds before I see the event in Kibana.  
Kibana is refreshing once per second.

Is there an explanation to the high number duration\_in\_millis?

Have I misunderstood what duration\_in\_millis means or is this a bug?

Kinds Regards  
Mathias

---

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [November 21, 2017, 1:08pm UTC](https://discuss.elastic.co/t/duration-in-millis-shows-too-high-values/108563/2 "2017-11-21T13:08:43Z")

</div>

I believe `duration_in_millis` is the total time across the number of events listed. 29552 ms across 4512 events is 6.54 ms per event. As multiple events are sent per batch and multiple batches can be sent in parallel, this does not directly relate to elapsed wall-time.

---

<div class="post-metadata">

### Author: ![mathias](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mathias/32/23176_2.png) [@mathias](https://discuss.elastic.co/u/mathias)
#### Post date: [November 22, 2017, 1:22pm UTC](https://discuss.elastic.co/t/duration-in-millis-shows-too-high-values/108563/3 "2017-11-22T13:22:49Z")

</div>

Thanks,

That explains a lot.

Br Mathias

---

<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: [December 20, 2017, 1:22pm UTC](https://discuss.elastic.co/t/duration-in-millis-shows-too-high-values/108563/4 "2017-12-20T13:22:51Z")

</div>

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