[Meta] Usage Collection: Add description field to schema

[afharo]

This issue is meant to group all the (cross-releases) action points related to adding the _meta.description fields to the usage collection schema.

• Add support to the initially-optional field ([Usage Collection] Add description field to schema #89685)
• Add the description fields to the Platform collectors (also [Usage Collection] Add description field to schema #89685)
• Create [Meta] issue to track all other teams' plugins to backfill the description to their fields (probably help them with the fields already described in our internal data dictionary @alexfrancoeur @thesmallestduck)
• (Optional) Somehow enforce the description addition to new fields.
• Make it mandatory after an agreed deadline.

[elasticmachine]

Pinging @elastic/kibana-telemetry (Team:KibanaTelemetry)

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[Bamieh]

LGTM!

[afharo]

#89726 would make great use of this initiative when implemented

[afharo]

Note: The main effort (supporting description fields in the schema) is completed. The rest is about chasing teams to fully document it and make it mandatory once we know the CI won’t break.

I don’t think this effort is pressing until #89726 is complete because we have no ways to leverage this info otherwise. Unless our Telemetry team says otherwise @mindbat @haywoood (I'm thinking on our internal indexer config UI)

[kpatticha]

In APM we started looking into it. The related PR - #157529

it seems #89726 is stale and we'd love to explore other possibilities if there is no plan to be tackled soon.

Other alternatives I could think

• Generate a table from the schamas, similar to have I have in [APM] Add description metadata to schema #157529 and make it available in enteprice search.
• Try the separate app using Enterprise search. The app is used already in analytics cluster. more information in the docs.

what do you think @afharo ?

[kpatticha]

• Try the separate app using Enterprise search. The app is used already in analytics cluster. more information in the docs.

it's far from the optimal solution we're aiming for as it requires adding the fields manually in the spreadsheet

[afharo]

I think @elastic/platform-analytics had something in mind for that.