in 6.0 _type is discontinued, but we can use custom field like "type" to index different types of objects in same index and then filter by that.
Is there any downside to this approach and store different documents types with differents fields in same index? or is better to use a different index per document type?
but metricbeat stores different structures for process utilization, flesystem ,network, psql etc in same metricbeat- index, doesnt it? why is not a problem there?
as i see metricbeat use the same root fields but then nested fields are totally different. Do you mean that if root fields are the same but not nested fields is fine to store in same index like these 2 docs from vmware module:
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.