Some Fleet-managed data streams not marked as such

[cjcenizal]

I followed the "How to test" steps from #83049 and noticed that a number of data streams aren't marked as Fleet-managed:

Looking at the data streams in Fleet, it looks like they are managed by Fleet:

@yuliacech Do you know what's going on here?

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[yuliacech]

Hi @cjcenizal , thanks for bringing this up! The UI relies on data stream metadata to label them as Fleet-managed and the metadata is inherited from the index template. Those data streams don't have an integration associated and fallback on the default index template for logs-* and similar. So they have managed:true but not managed-by:ingest-manager.

[cjcenizal]

@yuliacech Thanks for the explanation! Is the Fleet team already aware of this? If not would you mind getting this onto the Fleet team's radar, so they can decide whether or not they want to or are able to make any changes to apply managed-by:ingest-manager to these data streams?

[yuliacech]

Hi @cjcenizal , yes I checked with the Fleet team about those data streams not having managed-by:ingest-manager in their metadata object. But I'll confirm with them if they would like to update those data streams since users would get more consistent information in both apps. Thanks for bringing this up!

[sebelga]

Is this still an issue on our side? If/when the Fleet team decides to add the meta information on their datastream this issue will be solved, right @yuliacech ?

[yuliacech]

Closing this issue: the meta data for these data streams is now set correctly.