# Field is not matching anything in field list, but works correctly in 'table\_view'

**URL:** <https://discuss.elastic.co/t/field-is-not-matching-anything-in-field-list-but-works-correctly-in-table-view/15547>\
**Category:** Elasticsearch\
**Created:** [February 1, 2014, 10:03pm UTC](https://discuss.elastic.co/t/field-is-not-matching-anything-in-field-list-but-works-correctly-in-table-view/15547 "2014-02-01T22:03:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Glenn\_Poston](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/glenn_poston/32/1833_2.png) [@Glenn\_Poston](https://discuss.elastic.co/u/Glenn_Poston)\
**Post date:** [February 1, 2014, 10:03pm UTC](https://discuss.elastic.co/t/field-is-not-matching-anything-in-field-list-but-works-correctly-in-table-view/15547/1 "2014-02-01T22:03:39Z")

</div>

I've attached a screenshot from Kibana.

The screenshot shows a document that has a field named userIdentity.name.  
If I select the filter (magnifying glass), things work as expected.  
However in the field list on the left, this field does not show up.  
Instead there is a field called 'name.' When i select the filter  
(magnifying element) here there are no matches.

I've been working on this for a few days now and am completely stumped.  
Please help!

Here is the document json:

{  
"\_index": "logstash-2014.02.01",  
"\_type": "logs",  
"\_id": "tthuoePDSWKiWGtGz0hrwA",  
"\_score": null,  
"\_source": {  
"eventVersion": "1.0",  
"userIdentity": {  
"type": "IAMUser",  
"principalId": "xxxxx",  
"arn": "xxxxx",  
"accountId": "xxxx",  
"accessKeyId": "xxxx",  
"userName": "xxxxx"  
},  
"eventTime": "2014-02-01T21:52:16Z",  
"eventSource": "[ec2.amazonaws.com](http://ec2.amazonaws.com)",  
"eventName": "DescribeAddresses",  
"awsRegion": "us-east-1",  
"sourceIPAddress": "54.204.9.62",  
"userAgent": "aws-cli/1.2.6 Python/2.6.9 Linux/3.4.68-59.97.amzn1.x86\_64",  
"requestParameters": "{"publicIpsSet"=\>{}, "filterSet"=\>{}, "allocationIdsSet"=\>{}}",  
"responseElements": "nil",  
"@version": "1",  
"@timestamp": "2014-02-01T21:52:16.000Z",  
"environment": "test"  
},  
"sort": [  
1391291536000  
]  
}

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/662055b2-cedd-4604-b524-fa43c7f2241a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/662055b2-cedd-4604-b524-fa43c7f2241a%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Glenn\_Poston](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/glenn_poston/32/1833_2.png) [@Glenn\_Poston](https://discuss.elastic.co/u/Glenn_Poston)\
**Post date:** [February 1, 2014, 10:41pm UTC](https://discuss.elastic.co/t/field-is-not-matching-anything-in-field-list-but-works-correctly-in-table-view/15547/2 "2014-02-01T22:41:18Z")

</div>

Upgrading to milestone 4 resolved my issue. However, it appears that this  
release has it's own issue... albeit relatively minor compared to the first  
one. It's a css issue. Panel's in the logstash dashboard are white which  
prevents reading of the white text. I updated the follwing css element  
from #fff to #202328 fix.

css/bootstrap.light.min.css  
.panel-container {background: #202328}

On Saturday, February 1, 2014 5:03:39 PM UTC-5, Glenn Poston wrote:

> I've attached a screenshot from Kibana.
> 
> The screenshot shows a document that has a field named userIdentity.name.  
> If I select the filter (magnifying glass), things work as expected.  
> However in the field list on the left, this field does not show up.  
> Instead there is a field called 'name.' When i select the filter  
> (magnifying element) here there are no matches.
> 
> I've been working on this for a few days now and am completely stumped.  
> Please help!
> 
> Here is the document json:
> 
> {  
> "\_index": "logstash-2014.02.01",  
> "\_type": "logs",  
> "\_id": "tthuoePDSWKiWGtGz0hrwA",  
> "\_score": null,  
> "\_source": {  
> "eventVersion": "1.0",  
> "userIdentity": {  
> "type": "IAMUser",  
> "principalId": "xxxxx",  
> "arn": "xxxxx",  
> "accountId": "xxxx",  
> "accessKeyId": "xxxx",  
> "userName": "xxxxx"  
> },  
> "eventTime": "2014-02-01T21:52:16Z",  
> "eventSource": "[ec2.amazonaws.com](http://ec2.amazonaws.com)",  
> "eventName": "DescribeAddresses",  
> "awsRegion": "us-east-1",  
> "sourceIPAddress": "54.204.9.62",  
> "userAgent": "aws-cli/1.2.6 Python/2.6.9 Linux/3.4.68-59.97.amzn1.x86\_64",  
> "requestParameters": "{"publicIpsSet"=\>{}, "filterSet"=\>{}, "allocationIdsSet"=\>{}}",  
> "responseElements": "nil",  
> "@version": "1",  
> "@timestamp": "2014-02-01T21:52:16.000Z",  
> "environment": "test"  
> },  
> "sort": [  
> 1391291536000  
> ]  
> }

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/8a769dd9-b1d3-46a0-b2e8-32bb1d678b11%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8a769dd9-b1d3-46a0-b2e8-32bb1d678b11%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:** [July 6, 2017, 1:53am UTC](https://discuss.elastic.co/t/field-is-not-matching-anything-in-field-list-but-works-correctly-in-table-view/15547/3 "2017-07-06T01:53:26Z")

</div>


