-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Security Solution][Elastic AI Assistant] Refactors Knowledge Base feature flag to UI feature toggle #167935
Conversation
Pinging @elastic/security-solution (Team: SecuritySolution) |
.../kbn-elastic-assistant/impl/assistant/settings/use_settings_updater/use_settings_updater.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @spong for enabling the KB via the UI toggle! 🙏
✅ Desk tested locally
LGTM 🚀
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @spong |
Summary
This PR refactors the
assistantLangChain
code feature flag introduced in #164908, to be a UI feature toggle that users can enable/disable via theKnowledge Base
assistant advanced settings.Left image shows the feature disabled, and the right image shows the feature partly enabled. If ELSER is configured, the UI will attempt to install all resources automatically for a one-click UX, however if ELSER is not configured, or there are failures, the user can manually enable the Knowledge Base or ES|QL base documentation:
Also, since this code feature flag was shared with the model evaluator experimental feature, a
modelEvaluatorEnabled
flag has been plumbed to fully decouple the two settings. Now only the model evaluator is enabled when setting security Solution Advanced setting:and the previous
assistantLangChain
code feature flag is now enabled by simply toggling on the Knowledge Base in the settings shown above.Note
Even if ELSER isn't configured, and the knowledge base/docs aren't setup, if the Knowledge Base is enabled, the LangChain code path will still be enabled as intended, but we can change this behavior if testing shows this is not ideal.
Checklist
Delete any items that are not applicable to this PR.