# Multiple tiebreaker fields for logs
**URL:** https://discuss.elastic.co/t/multiple-tiebreaker-fields-for-logs/174982
**Category:** Kibana
**Created:** [April 2, 2019, 12:00pm UTC](https://discuss.elastic.co/t/multiple-tiebreaker-fields-for-logs/174982 "2019-04-02T12:00:10Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@OrangeDog](https://discuss.elastic.co/u/OrangeDog)
#### Post date: [April 2, 2019, 12:00pm UTC](https://discuss.elastic.co/t/multiple-tiebreaker-fields-for-logs/174982/1 "2019-04-02T12:00:11Z")
The property `config.xpack.infra.sources.default.fields.tiebreaker` only appears to support a single field, and Kibana will show "There are no log messages to display." if it's missing.
Instead it should support multiple, the same as `context:tieBreakerFields`. Especially as there's no built-in solution to generate sequence numbers in logstash if they're missing.
> A comma-separated list of fields to use for tiebreaking between documents that have the same timestamp value. From this list the first field that is present and sortable in the current index pattern is used.
Specifically I want to be able to set it to `seq,_doc`.
---
### Author:  [@Bill\_McConaghy](https://discuss.elastic.co/u/Bill_McConaghy)
#### Post date: [April 3, 2019, 3:29pm UTC](https://discuss.elastic.co/t/multiple-tiebreaker-fields-for-logs/174982/2 "2019-04-03T15:29:29Z")
I would suggest opening an issue for this at [https://github.com/elastic/kibana/issues](https://github.com/elastic/kibana/issues)
---
### Author:  [@OrangeDog](https://discuss.elastic.co/u/OrangeDog)
#### Post date: [April 8, 2019, 8:38am UTC](https://discuss.elastic.co/t/multiple-tiebreaker-fields-for-logs/174982/3 "2019-04-08T08:38:27Z")
>
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 6, 2019, 8:38am UTC](https://discuss.elastic.co/t/multiple-tiebreaker-fields-for-logs/174982/4 "2019-05-06T08:38:28Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.