# Some field is not showing in ML

**URL:** <https://discuss.elastic.co/t/some-field-is-not-showing-in-ml/112354>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-machine-learning\
**Created:** [December 19, 2017, 5:49am UTC](https://discuss.elastic.co/t/some-field-is-not-showing-in-ml/112354 "2017-12-19T05:49:33Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![tatdat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tatdat/32/113160_2.png) [@tatdat](https://discuss.elastic.co/u/tatdat)\
**Post date:** [December 19, 2017, 5:49am UTC](https://discuss.elastic.co/t/some-field-is-not-showing-in-ml/112354/1 "2017-12-19T05:49:33Z")

</div>

Im testing in Kibana + ES 6.1

Im following guide in this blog [https://www.elastic.co/blog/machine-learning-for-nginx-logs](https://www.elastic.co/blog/machine-learning-for-nginx-logs) - Use Case 2: Changes in Website Behaviour

But i cant see field "nginx.access.response" .. and this field existed data

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/7/a7458230a941f890bbc63ed9fec85924ad3173e3.png)

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/a/2a18b117e51926515472b941887e694eafd274ec.png)

---

<div class="post-metadata">

**Author:** ![tatdat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tatdat/32/113160_2.png) [@tatdat](https://discuss.elastic.co/u/tatdat)\
**Post date:** [December 20, 2017, 4:28am UTC](https://discuss.elastic.co/t/some-field-is-not-showing-in-ml/112354/2 "2017-12-20T04:28:59Z")

</div>

Can someone have suggestion?

---

<div class="post-metadata">

**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\
**Post date:** [December 20, 2017, 8:20pm UTC](https://discuss.elastic.co/t/some-field-is-not-showing-in-ml/112354/3 "2017-12-20T20:20:54Z")

</div>

What does the Index Pattern look like for nginx data? Go to Management -\> Index Pattern and select the nginx Index Pattern. Does the field `response_code` exist. If not, try hitting the "Refresh field list" button in the top left.

---

<div class="post-metadata">

**Author:** ![tatdat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tatdat/32/113160_2.png) [@tatdat](https://discuss.elastic.co/u/tatdat)\
**Post date:** [December 20, 2017, 11:53pm UTC](https://discuss.elastic.co/t/some-field-is-not-showing-in-ml/112354/4 "2017-12-20T23:53:35Z")

</div>

Hi @Nathan_Reese , of course, response\_code existed

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/f/1fd473065bab80c3b7134fddbb3dd9e2cb6cd7cd.png)

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/0/a0379aabdbab2ed80b51ecfc87a4e0cb5e4d51d2.png)

---

<div class="post-metadata">

**Author:** ![dkyle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dkyle/32/59114_2.png) [@dkyle](https://discuss.elastic.co/u/dkyle)\
**Post date:** [December 21, 2017, 2:15pm UTC](https://discuss.elastic.co/t/some-field-is-not-showing-in-ml/112354/5 "2017-12-21T14:15:52Z")

</div>

Hi,

You can't split a job by a numerical field due to the high cardinality of the field i.e. you could have billions of fields. Only text fields can be used to split data.

Is `nginx.access.response` also indexed as a `keyword` field? If so that should appear in the split data drop down list otherwise you will have to re-index the nginx data I'm afraid 😞

---

<div class="post-metadata">

**Author:** ![richcollier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/richcollier/32/115035_2.png) [@richcollier](https://discuss.elastic.co/u/richcollier)\
**Post date:** [December 21, 2017, 5:17pm UTC](https://discuss.elastic.co/t/some-field-is-not-showing-in-ml/112354/6 "2017-12-21T17:17:01Z")

</div>

The single and multi-metric job configuration UIs do indeed prevent users from selecting fields that are of type `number` as fields to "split by".

However, you can get around this by using the Advanced Job configuration - it has no such limitation:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/7/7751a20c9d7b26518c16890c486cafb69e52da62.png)

---

<div class="post-metadata">

**Author:** ![tatdat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tatdat/32/113160_2.png) [@tatdat](https://discuss.elastic.co/u/tatdat)\
**Post date:** [December 22, 2017, 4:53am UTC](https://discuss.elastic.co/t/some-field-is-not-showing-in-ml/112354/7 "2017-12-22T04:53:23Z")

</div>

Many thank @dkyle and @richcollier. I got it.

---

<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:** [January 19, 2018, 4:53am UTC](https://discuss.elastic.co/t/some-field-is-not-showing-in-ml/112354/8 "2018-01-19T04:53:31Z")

</div>

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