[UII] Add "Only agentless integrations" filter to integrations browse experience

[jen-huang]

Summary

Resolves https://github.com/elastic/ingest-dev/issues/5931. This PR adds a new toggle to Integrations browse page that only shows agentless integrations. A query param ?onlyAgentless=true is added if this toggle is enabled.

This toggle appears only if agentless is available for the deployment. It is placed above the existing show beta integrations toggle.

Default enabled view:

Persistence across deep filtering (with categories and search):

Release note

Added new filter to only show agentless integrations.

Checklist

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
• Review the backport guidelines and apply applicable backport:* labels.

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[MichelLosier]

Looking good so far, but it seems though the filtering is not aligning with the agentless check in deployment_modes. For example, when I have the agentless only filter on, I can still select the AWS ECS integration which doesn't support it.

[jen-huang]

I can still select the AWS ECS integration which doesn't support it.

Ah nice catch! I need to apply this filtering at the card level instead of at the package level. Taking a look.

[jen-huang]

@vishaangelova @karenzone any suggestions for improve the copy here or is it ok?

[karenzone]

For the filter: "Only agentless integrations"
If this format (starting with Only) matches wording for other filters. then 👍 .

For the message: "Agentless integrations run in Elastic Cloud without requiring you to deploy Elastic Agents"
We're using "Elastic Cloud Hosted" as the official platform name in docs, but shortening here might make sense. Are Agentless integrations available for Serverless?

[jen-huang]

If this format (starting with Only) matches wording for other filters. then 👍

we don't really have other similar filters. there is a similar toggle right below this one that says Display beta integrations, but that behaves differently (enabling it doesn't "only" show beta ones)

Are Agentless integrations available for Serverless?

yes they are! that's the reason why I chose Elastic Cloud since I believe that term covers both hosted + serverless?

[karenzone]

Fantastic on Hosted+Serverless. Makes sense. 👍

Filtering implies that a user is limiting or expanding their view based on other options selected. If a user selects only one category--like Agentless integrations--the "only" is implied.
In a filtering context, it seems that removing the word "only" makes sense. I'm interested to hear what you and others think.

[vishaangelova]

🤔 I see on the screenshots in the PR that these two toggles (Only agentless integrations and Display beta integrations) are meant to extend the filtering by category, so they enhance the filtering options: if you want to see the beta integrations, you enable the toggle. If you want to see only agentless integrations from a category, you enable the Only agentless integrations, right?

Personally, I think having only in the wording makes sense, and makes the functionality explicit, easy to understand. Without only I’m left to wonder whether it works as the Display beta integrations toggle - if I enable it, will it show the agentless integrations alongside the rest? Without only in the wording, I’d also expect that the default behavior is to not show the agentless integrations (similar to the beta integrations).

I also feel that having a verb such as Show or Display at the beginning would be nice - it would also be consistent in format with the Display beta integrations toggle. But at the same time, I’m conscious of the space used, so having Display only agentless integrations might be too long. If the latter is the case, I’d stick with Only agentless integrations.

[jen-huang]

thanks for the feedback @karenzone and @vishaangelova! (Visha, you hit the nail on the head about my conundrum with the behavior and copy)

I am going to merge this PR and leave the copy as it is for the above reasons, and also soon the entire filter experience here will be revamped and these confusing toggles will be replaced in favor of a "tag"-style filter UX: https://github.com/elastic/ingest-dev/issues/4789

[jen-huang]

@MichelLosier Fixed the filtering at the card level and updated the screenshots in this PR. This reduced the number of integrations from 90-something to 70ish. I assume most were non-agentless AWS ones like you mentioned :)

[MichelLosier]

LGTM!

I think the type check failure is just the state of main at the moment

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 7f9442d

Failed CI Steps

• FTR Configs #5
• FTR Configs #15

Test Failures

• [job] [logs] FTR Configs #15 / discover/group3 discover request counts ES|QL mode should send 2 requests (documents + chart) when changing the time range
• [job] [logs] FTR Configs #5 / security APIs - Session Lifespan Session Lifespan cleanup should properly clean up session expired because of lifespan when providers override global session config

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
fleet	1346	1347	+1

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
fleet	1512	1514	+2

Async chunks

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

id	before	after	diff
fleet	2.1MB	2.1MB	+1.5KB

Page load bundle

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

id	before	after	diff
fleet	175.8KB	175.9KB	+144.0B

Unknown metric groups

API count

id	before	after	diff
fleet	1644	1646	+2

History

• 💔 Build #341632 failed d46cc9c
• 💛 Build #341092 was flaky bfe8977

cc @jen-huang