You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently running "Kibana 3 milestone pre-3".
SIDE NOTE: Is there version number or some other information to specify which version we are using? In the latest version it no longer states the milestone in the top right corner.
Yesterday I tested the latest Kibana. In the Fields picker (part of Table Panel). It is showing unwanted fields; _all, _source, dynamic_template.0.string_template_mapping and dynamic_templates.0.string_template.
I poked around and found out if I changed my elasticsearch templates, it affects which fields are displayed.
I have it reduced to just showing _all and _source by removing the dyanmic_template sections from the Elasticsearch template.
I think the "dynamic_templates" feature is something you want to use in your elasticsearch templates, if you can't predict every property of your index. But showing them as fields in Kibana is somehow unnecessary, like showing a disabled _all field.
I am currently running "Kibana 3 milestone pre-3".
SIDE NOTE: Is there version number or some other information to specify which version we are using? In the latest version it no longer states the milestone in the top right corner.
Yesterday I tested the latest Kibana. In the Fields picker (part of Table Panel). It is showing unwanted fields; _all, _source, dynamic_template.0.string_template_mapping and dynamic_templates.0.string_template.
I poked around and found out if I changed my elasticsearch templates, it affects which fields are displayed.
I have it reduced to just showing _all and _source by removing the dyanmic_template sections from the Elasticsearch template.
Here is my elasticsearch template:
If I remove _all or _source from my template, then they do not show up in the Fields picker.
As stated in the beginning, I do not see this issue in the previous version of kibana 3. Only in the latest version.
Is there away to ignore unwanted fields?
Are the fields being pulled from mappings? If so, can we only pull the fields listed in properties?
The text was updated successfully, but these errors were encountered: