[Metrics UI] [Fleet] [R&D] Allow integrations to install Metrics UI saved views

[jasonrhodes]

Based on some of the work being done here #95885

We should investigate the feasibility of allowing packages to specify saved views that would be installed in the Metrics UI on package installation/upgrade. This would allow a package to immediately plug users into the Metrics UI based on their selection to "collect metrics" for the particular package. (Later, when we add Logs UI Saved Views, we can do the same for Logs UI!)

AC:

• Create an implementation ticket outlining clearer AC for what would need to be done so that:
  • A package could specify Metrics UI saved view(s) that would be installed on package installation/upgrade
  • Those view URLs would be linked from the asset list in the integration/package UI

[elasticmachine]

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

[elasticmachine]

Pinging @elastic/fleet (Feature:Fleet)

[elasticmachine]

Pinging @elastic/fleet (Feature:EPM)

[ruflin]

++ on adding support for metrics UI saved views to the packages. This will also need an issue in the package-spec repo to get it added to the spec: https://github.com/elastic/package-spec/blob/master/CONTRIBUTING.md#change-proposals

[simianhacker]

Here some thoughts:

• Kubernetes seems like an ideal candidate where the pods are grouped by namespace initially.
• It would be amazing if we could set the default screen for a host type to a saved view. For example, I would want Kubernetes Pods to use the "Grouped By Namespace" saved view by default. Where the EC2 view type to default to "Grouped by Availability Zone"

[sorantis]

I think this issue should also include the developer's perspective. Similar to how we create OOB dashboards today, the integration developer will need to be able to create a custom view in Kibana, save it and export it to a file that can later on be used as a package asset.

[jasonrhodes]

I think this issue should also include the developer's perspective

Can you say more about what you mean here?

[sorantis]

Sorry, I should've clarified. Today the job of creating content for our integrations (e.g. dashboards) is done by the integration developers. Saved views (as the intent is described here) would become part of the package content, much like dashboards are today. Since the integration developers are responsible for building content for integrations (except ML jobs), then I think the issue should cover the process from creating a saved view to making it part of the package.
For context, to provide an out-of-the-box dashboard today, one has to manually create visualizations in Kibana and arrange them on a dashboard, save the dashboard, and finally export it.

[elasticmachine]

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)