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

Elastic Stack Elasticsearch
1

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 to customize managed template settings; and
  • it uses the standard index mode instead of logsdb.

When I look at the source code 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?