# Warning about ambiguous (mutate filter + split)

**URL:** <https://discuss.elastic.co/t/warning-about-ambiguous-mutate-filter-split/248881>\
**Category:** Logstash\
**Created:** [September 16, 2020, 8:26pm UTC](https://discuss.elastic.co/t/warning-about-ambiguous-mutate-filter-split/248881 "2020-09-16T20:26:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dooger21](https://avatars.discourse-cdn.com/v4/letter/d/b4bc9f/32.png) [@dooger21](https://discuss.elastic.co/u/dooger21)\
**Post date:** [September 16, 2020, 8:26pm UTC](https://discuss.elastic.co/t/warning-about-ambiguous-mutate-filter-split/248881/1 "2020-09-16T20:26:43Z")

</div>

Hi everyone,

I have a Log that I read using the file plugin and the multiline codec (so far so good), I separate the columns that I want to get using a mutate and split in the filter, however in the execution of my .conf I see warnings that refer ambiguity in the fields (2). Please your help, what should I change in my code to avoid these warnings?

 ![warning](https://us1.discourse-cdn.com/elastic/original/3X/a/6/a68076fb3364ed1de6272aad3073ac32b7f3123c.png)

The warnings in text:  
[2020-09-16T16:09:09,410][WARN][org.logstash.FieldReference] Detected ambiguous Field Reference `message[0]`, which we expanded to the path `[message, 0]`; in a future release of Logstash, ambiguous Field References will not be expanded.  
[2020-09-16T16:09:09,414][WARN][org.logstash.FieldReference] Detected ambiguous Field Reference `message[2]`, which we expanded to the path `[message, 2]`; in a future release of Logstash, ambiguous Field References will not be expanded.  
[2020-09-16T16:09:09,460][WARN][org.logstash.FieldReference] Detected ambiguous Field Reference `message[4]`, which we expanded to the path `[message, 4]`; in a future release of Logstash, ambiguous Field References will not be expanded.  
[2020-09-16T16:09:09,460][WARN][org.logstash.FieldReference] Detected ambiguous Field Reference `message[6]`, which we expanded to the path `[message, 6]`; in a future release of Logstash, ambiguous Field References will not be expanded.

```auto

```

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [September 16, 2020, 9:14pm UTC](https://discuss.elastic.co/t/warning-about-ambiguous-mutate-filter-split/248881/2 "2020-09-16T21:14:16Z")

</div>

Please do not pictures of text. They are hard to read and impossible to search. Just post the text.

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [September 17, 2020, 3:29am UTC](https://discuss.elastic.co/t/warning-about-ambiguous-mutate-filter-split/248881/3 "2020-09-17T03:29:03Z")

</div>

You should access the index of the `message` field after the `split` filter using `[message][index]`, but you are using `message[index]`, this is probably the reason of your warning.

Change your pipeline to use `[message][index]` instead of `message[index]`.

---

<div class="post-metadata">

**Author:** ![dooger21](https://avatars.discourse-cdn.com/v4/letter/d/b4bc9f/32.png) [@dooger21](https://discuss.elastic.co/u/dooger21)\
**Post date:** [September 21, 2020, 4:33pm UTC](https://discuss.elastic.co/t/warning-about-ambiguous-mutate-filter-split/248881/4 "2020-09-21T16:33:12Z")

</div>

Its ok. Thanks @leandrojmp

---

<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:** [October 19, 2020, 4:33pm UTC](https://discuss.elastic.co/t/warning-about-ambiguous-mutate-filter-split/248881/5 "2020-10-19T16:33:27Z")

</div>

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