[Fleet] Show all integration assets on detail page

[jen-huang]

Summary

Resolves #160555.

This PR allows all assets to be shown on Integration details > Assets tab and links them to other apps in Kibana whenever possible for viewing. Previously, only dashboards, visualizations, and saved searches were shown in this view. Now all Kibana and Elasticsearch assets are shown if the integration was installed in the user's current space.

If an integration was installed in a different space, only ES assets will be shown.

Caveats

1. This page lists all assets tracked on the package installation saved object after the package is installed (installed_es and installed_kibana). This list differs from the summary of assets shown on the Overview tab because it includes Fleet-installed assets that are not part of the package, notably index templates, component templates, and default ingest pipelines. [Fleet] Package asset count differs after installation #182197 was created to decide how to resolve this asset count discrepency.

2. ML and Security assets are shown but not linked. The following issues have been created for downstream teams to decide where their assets should link to: [ML][Fleet] Link to ML assets from Integration > Assets tab #182199, [Security Solution][Fleet] Link to Security assets from Integration > Assets tab #182200

Screenshots

Nginx (including in a different space)

Security Posture Management

Rapid7 Threat Command

Lateral Movement Detection

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Unit or functional tests were updated or added to match the most common scenarios

[apmmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[jen-huang]

/ci

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[juliaElastic]

I am wondering if we could still display the ES assets in a different space, as those are not space aware e.g. if nginx was added to space A, index templates, ingest pipelines, etc. will be available in the default space too.

[kpollich]

I think we should try to display the ES assets regardless of the installed_kibana_space_id on the integration, as those assets are not tied to spaces.

[jen-huang]

great catch! I missed this part of the original code. thanks @juliaElastic

[juliaElastic]

LGTM, tested locally.

[kilfoyle]

LGTM for the docs. 👍

[jen-huang]

@kpollich @juliaElastic @nimarezainia I made adjustments for if the integration is installed in a different space. We can actually show the entire list of assets including the Kibana assets that belong in a different space, but only by ID and not name. I'm not sure if this is preferable over just hiding all the Kibana assets. What do you think?

[jen-huang]

@elasticmachine merge upstream

[kpollich]

I made adjustments for if the integration is installed in a different space. We can actually show the entire list of assets including the Kibana assets that belong in a different space, but only by ID and not name. I'm not sure if this is preferable over just hiding all the Kibana assets. What do you think?

I think I'd rather just hide the Kibana assets in other spaces, and just show the ES assets with along with the "Kibana assets are not available in this space" callout we already include. Semantically I think "Kibana assets aren't available, but here are the assets that are available" is the intent in spaces that aren't aligned with the installation's installed_kibana_space_id.

[jen-huang]

Thanks for the feedback @kpollich. I've made adjustments so that only ES assets are shown if Kibana assets were installed in a different space. We retain the callout about Kibana assets not being available in the current space.

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: a169f36
• Storybooks Preview

Failed CI Steps

• x-pack/test/alerting_api_integration/security_and_spaces/group1/config.ts

Test Failures

• [job] [logs] x-pack/test/alerting_api_integration/security_and_spaces/group1/config.ts / alerting api integration security and spaces enabled Alerts - Group 1 alerts find Actions should return the actions correctly

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
fleet	1.3MB	1.3MB	+251.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
fleet	159.9KB	160.8KB	+932.0B

History

• 💚 Build #207274 succeeded 09ba4db
• 💚 Build #207126 succeeded 7427d79
• 💔 Build #207092 failed 405acf5
• 💔 Build #207077 failed 1c85ab9

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream