[Agent Builder] Observability agent builder opt-in flow#245299
Merged
viduni94 merged 149 commits intoelastic:mainfrom Dec 15, 2025
Merged
[Agent Builder] Observability agent builder opt-in flow#245299viduni94 merged 149 commits intoelastic:mainfrom
viduni94 merged 149 commits intoelastic:mainfrom
Conversation
e observable with Chat Experience setting
This reverts commit c756dc5.
Contributor
Author
|
/ci-deploy |
neptunian
approved these changes
Dec 12, 2025
Contributor
Manual testing:
|
Contributor
Author
|
/ci-deploy |
Contributor
Author
|
/ci-deploy |
sorenlouv
approved these changes
Dec 15, 2025
Contributor
Author
Thank you @arturoliduena |
Contributor
⏳ Build in-progress
Failed CI StepsTest Failures
History
cc @viduni94 |
2 tasks
Merged
1 task
Zacqary
added a commit
that referenced
this pull request
Dec 18, 2025
…ntationUtil plugin (#246628) ## Summary Moves the panel placement registry from the `dashboard` plugin into the `presentationUtil` plugin. This is necessary to avoid circular dependency issues in the [Controls Anywhere project](#245588). ### Background Controls Anywhere introduces the concept of dashboard controls being rendered as movable panels. For this, we need to define their `PanelPlacementStrategy`: creating them with a very short height, medium width, and in the top left corner of the dashboard. This required adding the `dashboard` plugin as a `requiredPlugin` for `controls`. Unfortunately, #245299 introduced `onechat` as a dependency to `observabilityAIAssistant`, triggering this circular dependency cycle: ``` │ERROR Detected circular dependencies: │ERROR dashboard -> observabilityAIAssistant -> onechat -> stackConnectors -> triggersActionsUi -> controls -> dashboard │ERROR triggersActionsUi -> controls -> dashboard -> observabilityAIAssistant -> onechat -> triggersActionsUi │ERROR workflowsManagement -> triggersActionsUi -> controls -> dashboard -> observabilityAIAssistant -> onechat -> workflowsManagement │ERROR stackConnectors -> triggersActionsUi -> controls -> dashboard -> observabilityAIAssistant -> onechat -> workflowsManagement -> stackConnectors ``` Unfortunately, Kibana architecture doesn't have a good way of moving registries into `@kbn` packages yet, so we need to find a safer plugin for it to live in. We determined that `controls` and `dashboard` both depend on the `presentationUtil` plugin without incident, and it's already a place to put other miscellaneous dashboard-related things. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes https://github.com/elastic/obs-ai-team/issues/393
Closes https://github.com/elastic/obs-ai-team/issues/415
Summary
This PR implements the opt-in flow for agent builder from the Obs AI Assistant.
It's currently behind a feature flag that the ai-infra team introduced:
New Additions
observabilityAgent.enabled)classicandobservabilityspaces)useIsAgentBuilderEnabled)Note: The tour callout and "Try AI Agent" button to opt-in to agent builder will only be displayed ONLY if
When the chat experience is set to AI Agent
enabledflag in plugin start)The "Agents" nav link is added to serverless Observabilty projects and Obs solution nav for ECH:
Checklist
release_note:*label is applied per the guidelinesbackport:*labels.