# PacketBeat - negative responsetime

**URL:** <https://discuss.elastic.co/t/packetbeat-negative-responsetime/98094>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [August 23, 2017, 2:08pm UTC](https://discuss.elastic.co/t/packetbeat-negative-responsetime/98094 "2017-08-23T14:08:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rosselg](https://avatars.discourse-cdn.com/v4/letter/r/f14d63/32.png) [@rosselg](https://discuss.elastic.co/u/rosselg)\
**Post date:** [August 23, 2017, 2:08pm UTC](https://discuss.elastic.co/t/packetbeat-negative-responsetime/98094/1 "2017-08-23T14:08:57Z")

</div>

Hi,  
I've installed packetbeat Version 5.5.2 on a mysql node and I get negative responsetime in Kibana.

My config (simplified) is the following:

#================================== Flows =====================================  
packetbeat.flows:  
enabled: false

#========================== Transaction protocols =============================  
packetbeat.protocols.mysql:  
ports: [3306]

#================================ processor =====================================  
processors:

- drop\_event:  
when:  
range:  
responsetime.gte: 0  
responsetime.lte: 1000

#-------------------------- Elasticsearch output ------------------------------  
output.elasticsearch:  
hosts: ["elaticSearch:9200"]

Any idea how to avoid this behavior (I saw older thread, but no one matched my version)

Many thanks in advance!  
Greg

---

<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:** [September 20, 2017, 2:09pm UTC](https://discuss.elastic.co/t/packetbeat-negative-responsetime/98094/2 "2017-09-20T14:09:23Z")

</div>

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