# Why doesn't the index template created by .NET logger use logs@custom?

**URL:** <https://discuss.elastic.co/t/why-doesnt-the-index-template-created-by-net-logger-use-logs-custom/375953>\
**Category:** Elasticsearch\
**Created:** [March 14, 2025, 7:21pm UTC](https://discuss.elastic.co/t/why-doesnt-the-index-template-created-by-net-logger-use-logs-custom/375953 "2025-03-14T19:21:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tobiasly](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tobiasly/32/142067_2.png) [@tobiasly](https://discuss.elastic.co/u/tobiasly)\
**Post date:** [March 14, 2025, 7:21pm UTC](https://discuss.elastic.co/t/why-doesnt-the-index-template-created-by-net-logger-use-logs-custom/375953/1 "2025-03-14T19:21:02Z")

</div>

I'm using the `Elastic.Extensions.Logging` library to ship logs from my .NET app. When I configured it to bootstrap the data stream, it created a corresponding index template named `logs-dotnet-8.11.0` with a higher priority than the built-in `logs` index template.

I notice at least two problems with this index template, when compared to the built-in `logs` template:

- it does not include `logs@custom` in its list of component templates, which is the [recommended way](https://www.elastic.co/guide/en/observability/current/logs-index-template.html) to customize managed template settings; and
- it uses the standard index mode instead of `logsdb`.

When I [look at the source code](https://github.com/elastic/ecs-dotnet/blob/main/src/Elastic.CommonSchema/IndexTemplates.Generated.cs) for this library, the logic to create this template has not been updated since April 2024.

So my question is, are there any benefits I'm missing to using this `logs-dotnet-8.11.0` index template that the library created? Or should I delete it & let it fall back to the default `logs` template?