How to add fileds to index pattren , so it can be filterd by in discover search

[umen]

i defined simple index pattern " filebeat-*"
and it has only a few fields which i can filter by:

now i like to add new fields to this index pattern. which i can see they exist

but i can't find anywhere how to add them so i could get the data that i could filter by
what I'm missing here?

for example i like to add :
kubernetes.pod.name
and
kubernetes.container.name

so i cloud do search like :
kubernetes.pod.name : "my-pod-nameX"

i followed this tutorial:

Run Filebeat on Kubernetes | Filebeat Reference [7.10] | Elastic

and i do see all the logs in kibana

[flash1293 (Joe Reuter)]

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.

[umen]

Thanks for answering
Do you have idea why i can't get the value of the kubernetes.pod.name?
As i can see the info in the logs ?

[flash1293 (Joe Reuter)]

I don't understand your question, can you explain what you seeing and what you expect to see?

[umen]

hey
thanks for answering i would happily explain more if i could make it work, as my installation have a lot of problems
see here :

DNS lookup failure "my-cluster-es-http": lookup my-cluster-es-http on 1xx.xx.xx.xx:53: no such host

Hey i followed the quickstart tutorial to setup elasticsearch on Kubernetes . installed it on pre created namespace not default . apiVersion: elasticsearch.k8s.elastic.co/v1 kind: Elasticsearch metadata: name: my-cluster namespace: test-cluster spec: version: 7.10.1 nodeSets: - name: default count: 3 config: node.master: true node.data: true node.ingest: true node.store.allow_mmap: false now in filebeat-kubernetes.yaml i set : env: - name: E…

[flash1293 (Joe Reuter)]

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.

[umen]

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