Document unified integrations view guidelines for future package development

[akshay-saraswat]

In 7.16, the Kibana team is planning to introduce the unified integrations view. And this view will aim to improve the discoverability of integrations by providing a uniform one-stop source for both beats and agent-based integrations. Integration teams associated with each Elastic app will work on updating the existing packages. But we need to capture these guidelines somewhere for future package development so that developers don't forget to align integration title and description with unified integrations view guidelines.

[jlind23]

@akshay-saraswat should we simply "enforce" through package spec the fields that are mandatory regarding the unified integrations?
ping @mtojek @jsoriano

[jsoriano]

Do we have a list of recommendations from the Kibana team? If some of the guidelines are more "aesthetic" then it may be difficult (or impossible) to enforce with tooling.

[akshay-saraswat]

@akshay-saraswat should we simply "enforce" through package spec the fields that are mandatory regarding the unified integrations? ping @mtojek @jsoriano

Guidelines are mostly around the format of title and description.
For example, Linux integration card currently has the following
Title: Linux
Description: Linux Integration

Guidelines will make it consistent with other integration cards
Title: Linux Metrics
Description: Collect metrics from Linux servers with Elastic Agent.

We are mentioning "Metrics" or "Logs" in the title when the integration collects specific data formats. And description is supposed in this format - Collect from with .

I agree with @jsoriano it will be difficult to enforce the format.