# Why multi-fields display in kibana?

**URL:** https://discuss.elastic.co/t/why-multi-fields-display-in-kibana/376206
**Category:** Kibana
**Created:** [March 20, 2025, 9:47pm UTC](https://discuss.elastic.co/t/why-multi-fields-display-in-kibana/376206 "2025-03-20T21:47:08Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Anson5](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anson5/32/133152_2.png) [@Anson5](https://discuss.elastic.co/u/Anson5)
#### Post date: [March 20, 2025, 9:47pm UTC](https://discuss.elastic.co/t/why-multi-fields-display-in-kibana/376206/1 "2025-03-20T21:47:08Z")

</div>

I have three indexes: `ta-logs-info`, `ta-logs-error`, and `ta-logs-trace`, all using the same mapping. I’ve also created four different index patterns:

- `ta-logs-info`
- `ta-logs-error`
- `ta-logs-trace`
- `ta-logs*` (covering all three indexes)

When searching logs under the `ta-logs*` index pattern, it retrieves messages from `ta-logs-info`, `ta-logs-error`, and `ta-logs-trace`. However, fields like `host.hostname` and `log.level` appear as multi-fields, while other fields do not.

In contrast, when using the `ta-logs-info` index pattern, `host.hostname` and `log.level` do not appear as multi-fields.

Can someone explain why this happens?

 ![multi-fields](https://us1.discourse-cdn.com/elastic/original/3X/1/c/1c459f8f67a1d3d7f3074b0bddff434d07e515d0.png)