I think Kibana can't cache object field with dynamic set to false.
I create a new mapping with dynamic to true and delete the type object. After that, fields are available.
My concern is the impact on embedded monitoring features.
Doesanyone know if there is an impact to Elasticsearch/Kibana monitoring features?
The mappings are setup for .monitoring-* indices such that all mapped fields are used in the Stack Monitoring UI. It is true that were are more fields in the document than are in the mapping.
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.