[9.3] [Obs AI] Use the Observability Agent in AI Insights and flyout config (#249776)#249915
Merged
kibanamachine merged 1 commit intoelastic:9.3from Jan 21, 2026
Merged
Conversation
…elastic#249776) Closes elastic/obs-ai-team#469 ## Summary This PR updates the agent used for Observability AI Insights and the active flyout config in Observability pages to use the Obs Agent. The reason for this change is because we want to benefit from all the tools and instructions in the Obs Agent which caters specifically for Observability signals. In addition to the above, this PR also removes the `platform.core.search` tool from the Obs Agent for the following reasons: - **High failure rate** - This tool fails on observability indices because they lack text or semantic_text field mappings, resulting in frequent "No text or semantic_text fields found" errors. - **Token/Cost wastage** - Failed tool calls consume tokens and increase latency without providing value, often triggering unnecessary retries - **Redundant** - The observability agent already has specialized tools (`get_correlated_logs`, `get_trace_metrics`, `get_services`, `get_index_info`, etc.) designed specifically for observability data. - Better tool selection by the LLM - Removing this tool allows the LLM to select more reliable specialized tools, improving the success rate and completion time. ### Log AI Insights https://github.com/user-attachments/assets/8c988b1c-4fb1-4317-bea7-23f4a83e5d0f ### Alert AI Insights https://github.com/user-attachments/assets/83fbcf35-6ca1-451a-9e48-1c35fe697058 ### Error AI Insights https://github.com/user-attachments/assets/e2937ab0-98ee-4212-91e0-fa69962e6754 ### Checklist - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. (cherry picked from commit 09d2490)
botelastic
Bot
added
Team:obs-presentation
2 tasks
Contributor
|
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
Contributor
|
Pinging @elastic/obs-presentation-team (Team:obs-presentation) |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Public APIs missing comments
Async chunks
Page load bundle
cc @viduni94 |
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
3 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.
Backport
This will backport the following commits from
mainto9.3:Questions ?
Please refer to the Backport tool documentation