due to deprecation of old Custom Logs integration I'm now configuring the new Custom Logs (Filestream) integration, and I'm wondering why this integration does not create a managed dataset specific index template like other custom integrations do.
The new Data Stream was automatically configured to use the generic logs template, but I don't want to extend it with dataset specific index mappings.
Is the any way to make Fleet create managed index template for this integration?
Clone the logs template and update it to your needs...
I think we stopped auto creating templates... as often they added little to no value, so now it is "by intention"
thanks for a quick response. Sounds like a valid point. For me it was important to know if it's a new pattern or something specific for this integration.
The auto creation of templates is more user friendly and was very helpful for me in the learning phase, as I could implement my solution without knowing much about links between data stream, index template and component templates.
A how-to-guide for using custom integration agents would be helpful for elastic newbies, I think.
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.
