The field list in discover is sampled from the first 500 documents - if the field doesn't have a value in these documents, it won't show up. You can show the complete list based on the mapping by clicking "Filter by type" and unchecking "Hide missing fields".
Alternatively you can add a new filter below the search bar and just use the field (it will show up in the suggestions of the field input) - this will make sure the 500 documents contain that field and it will also show up in the sidebar.
As Kibana is the top of the stack, it probably makes sense to resolve all problems in the lower levels first before coming back to troubleshoot Kibana. In a lot of cases the problems aren't even caused by Kibana in the first place but the data itself is not in order in Elasticsearch.
thanks for answering, sure you are right, the problem is that it just stopped working after and uninstall it once and installed it again but this time with a custom namespace, then everything stopped to work.
this question from my first install with the "default" namespace. as we not allowed to use the "default" namespace.
and even then it didn't get me all the info . like
kubernetes.pod.name
kubernetes.container.name
i saw allot of questions regarding the DNS with out any answer .. so I'm afraid my case will be the same
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.