There are at least some metric related integrations that have templates that use the text field type.
When these integrations are migrated to tsdb, then often this fails initially complaining with the error that text field either needs a subfield of type keyword or should be stored (by setting store=true, enabling stored fields for this field specifically).
This is a bit confusing sometimes, because the error doesn't come from ES directly and takes time to figure out what needs to be changed.

There are two options here, remove the text field from template when upgrading to tsdb or make suggested changes to the field of type text. What often happens is that store is set to true. However if this is always the intended approach for integrations, should Elasticsearch change the default of store to true for tsdb?

Relates to #96254