# Available fields in kibana

**URL:** <https://discuss.elastic.co/t/available-fields-in-kibana/214864>\
**Category:** Kibana\
**Created:** [January 13, 2020, 3:50pm UTC](https://discuss.elastic.co/t/available-fields-in-kibana/214864 "2020-01-13T15:50:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![volcano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/volcano/32/46287_2.png) [@volcano](https://discuss.elastic.co/u/volcano)\
**Post date:** [January 13, 2020, 3:50pm UTC](https://discuss.elastic.co/t/available-fields-in-kibana/214864/1 "2020-01-13T15:50:04Z")

</div>

Here is this entry in logstash.conf

```auto
mutate {
       split => ["message","Employee"]
       add_field => {"part1" =>"%{[message][0]}"}
       add_field => {"part2" =>"%{[message][1]}"}      
}

mutate {
       split => ["part2","#"]
       add_field => {"part2_1" =>"%{[part2][0]}"}
       add_field => {"part2_2" =>"%{[part2][1]}"}

```

}

This adds part1 , part2 , part2\_1 and part2\_2 fields in Kibana's Available field list.

But my requirement is to add only part2\_2 field . rest of the fields are not required in Kibana.

What changes I should make here so that only part2\_2 field is added in Kibana's Available field list.

---

<div class="post-metadata">

**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\
**Post date:** [January 14, 2020, 2:19am UTC](https://discuss.elastic.co/t/available-fields-in-kibana/214864/2 "2020-01-14T02:19:47Z")

</div>

Hello @volcano - Which version of the elastic stack are you running? Do you need those fields to be in elasticsearch aside from usage in Kibana?

---

<div class="post-metadata">

**Author:** ![volcano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/volcano/32/46287_2.png) [@volcano](https://discuss.elastic.co/u/volcano)\
**Post date:** [January 14, 2020, 4:35am UTC](https://discuss.elastic.co/t/available-fields-in-kibana/214864/3 "2020-01-14T04:35:00Z")

</div>

I dont want field **part1** to be pushed to elasticsearch and then to Kibana. I want only **part2** to be pushed to elastic search and kibana.

I am worried about the syntax. I am changing this way

From this...

```
        mutate {
               split => ["message","Employee"]
               add_field => {"part1" =>"%{[message][0]}"}
               add_field => {"part2" =>"%{[message][1]}"}      
        }

```

To this

```
mutate {
       split => ["message","Employee"]
       part1 =>"%{[message][0]}"}
       add_field => {"part2" =>"%{[message][1]}"}      
}

```

look at **part1** above . Is this correct syntax not to add the field? I am stuck at this spot.

I am using elastic search managed service in AWS . version 7.1.1

---

<div class="post-metadata">

**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\
**Post date:** [January 14, 2020, 11:16pm UTC](https://discuss.elastic.co/t/available-fields-in-kibana/214864/4 "2020-01-14T23:16:25Z")

</div>

I wonder if the dissect filter would be simpler - [https://www.elastic.co/guide/en/logstash/7.1/plugins-filters-dissect.html](https://www.elastic.co/guide/en/logstash/7.1/plugins-filters-dissect.html)

---

<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 11, 2020, 11:16pm UTC](https://discuss.elastic.co/t/available-fields-in-kibana/214864/5 "2020-02-11T23:16:34Z")

</div>

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