[Search] Search assistant plugin setup

[saarikabhasi]

Summary

Introducing new plugin for search assistant. in the future this will be extension of Observability AI solution solution plugin

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

[ryankeairns]

Only reviewed CSS changes on behalf of kibana-design; added a file

[jbudz]

packages/kbn-optimizer/limits.yml

[sphilipse]

Thanks, Saarika! I left a few comments to clean up, there's some stuff in here that doesn't need to be there (yet), but if we delete that we can merge this.

[saarikabhasi]

@elasticmachine merge upstream

[saarikabhasi]

@elasticmachine merge upstream

[jeramysoucy]

I was unable to start Kibana from this PR.
Error: Cannot find module '/x-pack/plugins/search_assistant/server'
Am I perhaps missing part of the plugin build process?

Some other basic questions:

• What is the purpose of the plugin? As a future extension to the Observability Assistant plugin, what will it add?
• Who will be able to access this plugin? What privileges are required?
• This plugin is currently empty, but if there are plans to introduce HTTP API endpoints, loggers, API keys, or Saved Objects, please consider the appropriate security measures (validation, privileges, logging level, any sensitive information).

[sphilipse]

I was unable to start Kibana from this PR. Error: Cannot find module '/x-pack/plugins/search_assistant/server' Am I perhaps missing part of the plugin build process?

Yeah we're missing server/index.ts right now.

Some other basic questions:

• What is the purpose of the plugin? As a future extension to the Observability Assistant plugin, what will it add?

We're building a Search-specific assistant that will run in ES3 and Search. It'll have different system prompts, different functions and different quick prompts at minimum, and likely different other extensions over time. But we want to share as much as possible of the backend and components with the Observability AI Assistant. Next steps would be:

• Abstracting shareable components outside of the Obs AI Assistant code and sharing them between these two plugins (likely in a third plugin or a package)
• Wiring this into the server of the Obs AI Assistant where possible
• Showing this AI assistant in Search and ES3 (when enabled)

• Who will be able to access this plugin? What privileges are required?

TBD, I want to keep that out of this PR for now. There's a lot we still need to decide on and this is just an initial starting point.

• This plugin is currently empty, but if there are plans to introduce HTTP API endpoints, loggers, API keys, or Saved Objects, please consider the appropriate security measures (validation, privileges, logging level, any sensitive information).

Yup, will do. Out of scope for this PR.

[saarikabhasi]

@elasticmachine merge upstream

[jeramysoucy]

Thanks for the details @sphilipse and updates @saarikabhasi! Unless I am missing something, the plugin appears to be enabled by default. There was a xpack.searchAssistant.ui.enabled setting, but that did not allow me to disable the pluigin. Additionally, it looks like that setting was removed.

Happy to approve once the plugin is disabled by default for all offerings. This will ensure that main is in a releasable state for serverless.

[sphilipse]

Thanks for the details @sphilipse and updates @saarikabhasi! Unless I am missing something, the plugin appears to be enabled by default. There was a xpack.searchAssistant.ui.enabled setting, but that did not allow me to disable the pluigin. Additionally, it looks like that setting was removed.

Happy to approve once the plugin is disabled by default for all offerings. This will ensure that main is in a releasable state for serverless.

Done in 7f17d49 @jeramysoucy

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: ad2a81a

Failed CI Steps

• FTR Configs #46

Test Failures

• [job] [logs] FTR Configs #46 / machine learning - data visualizer esql data visualizer with farequote ES|QL farequote displays index details

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
searchAssistant	-	4	+4

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
searchAssistant	-	6	+6

Page load bundle

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

id	before	after	diff
searchAssistant	-	1.5KB	+1.5KB

Unknown metric groups

API count

id	before	after	diff
searchAssistant	-	6	+6

ESLint disabled line counts

id	before	after	diff
searchAssistant	-	4	+4

Total ESLint disabled count

id	before	after	diff
searchAssistant	-	4	+4

History

• 💚 Build #228939 succeeded de3cb3c
• 💔 Build #228917 failed 6222df9
• 💔 Build #228615 failed 3adcb0e
• 💔 Build #228608 failed 4d9af48
• 💔 Build #228359 failed 0bbf057
• 💔 Build #228321 failed 07b7067

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