# Filebeat:Events in Kibana not in Sequence

**URL:** <https://discuss.elastic.co/t/filebeat-events-in-kibana-not-in-sequence/72464>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 23, 2017, 10:35am UTC](https://discuss.elastic.co/t/filebeat-events-in-kibana-not-in-sequence/72464 "2017-01-23T10:35:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ARD](https://avatars.discourse-cdn.com/v4/letter/a/6f9a4e/32.png) [@ARD](https://discuss.elastic.co/u/ARD)\
**Post date:** [January 23, 2017, 10:35am UTC](https://discuss.elastic.co/t/filebeat-events-in-kibana-not-in-sequence/72464/1 "2017-01-23T10:35:13Z")

</div>

I have configured filebeat to a kafka output which is subsequently fed to elastic and then visualized in kibana.  
ApplicationLogfile--\>Filebeat--\>kafka--\>logstash--\>Kibana

The issue is, when the Application writes events in Log files the result in kibana is not in sequence.

I have tried with a fileoutput and the result in the file is perfectly in sequence.

I have the following config in filebeat.yml  
output.kafka:  
hosts: ["XX.XX.XXX.X:9092","XX.XX.XXX.X:9092","XX.XX.XXX.X:9092"]  
topic: "XYZ-logging-XYZApplication"  
required\_acks: 1  
output.file:  
path: "/data/apps"  
filename: filebeat

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [January 23, 2017, 12:39pm UTC](https://discuss.elastic.co/t/filebeat-events-in-kibana-not-in-sequence/72464/2 "2017-01-23T12:39:58Z")

</div>

it's partially of how kafka operates. Kafka splits a topic into multiple partitions. All partitions act like concurrent queues (there is no ordering guarantees between partitions). By default the kafka output uses random partition selection, selecting a new partition for every event. You can increase the number of events being pushed to one partition, before selecting another one, but in general this behavior is due to load-balancing. Normally you should be able to sort events by timestamp and offset in kibana.

---

<div class="post-metadata">

**Author:** ![ARD](https://avatars.discourse-cdn.com/v4/letter/a/6f9a4e/32.png) [@ARD](https://discuss.elastic.co/u/ARD)\
**Post date:** [January 23, 2017, 12:53pm UTC](https://discuss.elastic.co/t/filebeat-events-in-kibana-not-in-sequence/72464/3 "2017-01-23T12:53:38Z")

</div>

thanks steffens, Can I sort the table in kibana on both timestamp and offset ? I thought only one field sort was possible ?

---

<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:** [February 20, 2017, 12:53pm UTC](https://discuss.elastic.co/t/filebeat-events-in-kibana-not-in-sequence/72464/4 "2017-02-20T12:53:40Z")

</div>

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