# Negative MongoDB responsetime

**URL:** <https://discuss.elastic.co/t/negative-mongodb-responsetime/28157>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [August 27, 2015, 7:32am UTC](https://discuss.elastic.co/t/negative-mongodb-responsetime/28157 "2015-08-27T07:32:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Augustin\_Chen](https://avatars.discourse-cdn.com/v4/letter/a/b5ac83/32.png) [@Augustin\_Chen](https://discuss.elastic.co/u/Augustin_Chen)\
**Post date:** [August 27, 2015, 7:32am UTC](https://discuss.elastic.co/t/negative-mongodb-responsetime/28157/1 "2015-08-27T07:32:31Z")

</div>

Hi,  
I install the packetbeat-1.0.0-beta2-x86\_64.rpm in my MongoDB instance. I notice the negative response time in the kibana. Any ideas of this?

 ![](https://us1.discourse-cdn.com/elastic/original/2X/6/662636bf2c1d6b2e04c944a2ae6c8536c57d55f3.jpg)

---

<div class="post-metadata">

**Author:** ![Augustin\_Chen](https://avatars.discourse-cdn.com/v4/letter/a/b5ac83/32.png) [@Augustin\_Chen](https://discuss.elastic.co/u/Augustin_Chen)\
**Post date:** [August 31, 2015, 6:11am UTC](https://discuss.elastic.co/t/negative-mongodb-responsetime/28157/2 "2015-08-31T06:11:42Z")

</div>

@tudor Any ideas of this this issue?

In the packetbeat demo, I don't see any negative responsetime.

[http://demo.elastic.co/packetbeat/#/discover/MongoDB-transactions?\_g=()&\_a=(columns:!(method,type,path,responsetime,status,query),filters:!(](http://demo.elastic.co/packetbeat/#/discover/MongoDB-transactions?_g=()&_a=(columns:!(method,type,path,responsetime,status,query),filters:!()(meta:(disabled:!f,index:'packetbeat-_',key:type,negate:!f,value:mongodb),query:(match:(type:(query:mongodb,type:phrase))))),index:'packetbeat-_',interval:auto,query:(query\_string:(analyze\_wildcard:!t,query:'\*')),sort:!(timestamp,desc))

The mongodb instance you use for this demo appears to be standalone instances, not a replica-set. Does this affect the responsetime?

---

<div class="post-metadata">

**Author:** ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)\
**Post date:** [August 31, 2015, 8:10am UTC](https://discuss.elastic.co/t/negative-mongodb-responsetime/28157/3 "2015-08-31T08:10:41Z")

</div>

That shouldn't happen (well, obviously). It might be some overflow, but I didn't yet investigate. Would you mind opening up a ticket for it on Github adding any information that might be relevant? We'll be looking at this with priority.

---

<div class="post-metadata">

**Author:** ![Augustin\_Chen](https://avatars.discourse-cdn.com/v4/letter/a/b5ac83/32.png) [@Augustin\_Chen](https://discuss.elastic.co/u/Augustin_Chen)\
**Post date:** [September 1, 2015, 5:24am UTC](https://discuss.elastic.co/t/negative-mongodb-responsetime/28157/4 "2015-09-01T05:24:54Z")

</div>

The ticket is created. [https://github.com/elastic/packetbeat/issues/216](https://github.com/elastic/packetbeat/issues/216)

---

<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 5, 2017, 9:58pm UTC](https://discuss.elastic.co/t/negative-mongodb-responsetime/28157/5 "2017-07-05T21:58:52Z")

</div>