# New Custom Logs (Filestream) integration does not create a dataset specific index template

**URL:** <https://discuss.elastic.co/t/new-custom-logs-filestream-integration-does-not-create-a-dataset-specific-index-template/380179>\
**Category:** Elastic Agent\
**Tags:** fleet, integrations\
**Created:** [July 16, 2025, 1:07pm UTC](https://discuss.elastic.co/t/new-custom-logs-filestream-integration-does-not-create-a-dataset-specific-index-template/380179 "2025-07-16T13:07:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![allatrue](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allatrue/32/130067_2.png) [@allatrue](https://discuss.elastic.co/u/allatrue)\
**Post date:** [July 16, 2025, 1:07pm UTC](https://discuss.elastic.co/t/new-custom-logs-filestream-integration-does-not-create-a-dataset-specific-index-template/380179/1 "2025-07-16T13:07:55Z")

</div>

Hello Everyone,

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?

My stack version is 9.0.1

Thanks.

Regards,  
Alexander

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [July 16, 2025, 11:27pm UTC](https://discuss.elastic.co/t/new-custom-logs-filestream-integration-does-not-create-a-dataset-specific-index-template/380179/2 "2025-07-16T23:27:42Z")

</div>

Hi @allatrue

I think the pattern is now...

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"

 ![Screenshot 2025-07-16 at 4.25.30 PM](https://us1.discourse-cdn.com/elastic/original/3X/1/8/18654d8bdf39d0629f79562b993b306da9eb6572.png)

To match your integration

 ![Screenshot 2025-07-16 at 4.26.24 PM](https://us1.discourse-cdn.com/elastic/original/3X/2/c/2c69cdb0cc9eee25bb0171ba6994a7e9960a226f.png)

---

<div class="post-metadata">

**Author:** ![allatrue](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allatrue/32/130067_2.png) [@allatrue](https://discuss.elastic.co/u/allatrue)\
**Post date:** [July 17, 2025, 6:57am UTC](https://discuss.elastic.co/t/new-custom-logs-filestream-integration-does-not-create-a-dataset-specific-index-template/380179/3 "2025-07-17T06:57:10Z")

</div>

Dear @stephenb,

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.

Regards,  
Alexander