[Obs AI] get_log_categories tool: Rename terms to kqlFilter for consistency#248477
Merged
sorenlouv merged 2 commits intoelastic:mainfrom Jan 9, 2026
Merged
[Obs AI] get_log_categories tool: Rename terms to kqlFilter for consistency#248477sorenlouv merged 2 commits intoelastic:mainfrom
get_log_categories tool: Rename terms to kqlFilter for consistency#248477sorenlouv merged 2 commits intoelastic:mainfrom
Conversation
3 tasks
sorenlouv
added
backport:version
Contributor
💔 Build Failed
Failed CI Steps |
viduni94
approved these changes
Jan 9, 2026
Contributor
|
Starting backport for target branches: 9.3 https://github.com/elastic/kibana/actions/runs/20865121853 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jan 9, 2026
… consistency (elastic#248477) Tools should use standardized terminology for the same operations. `kqlFilter` is now a common tool param across most of the o11y tools. This renames `terms` param to `kqlFilter` param. This also introduces `fields` param that enables the LLM to specify which fields should be returned in the response. (cherry picked from commit 1ab14d0)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Jan 9, 2026
…r` for consistency (#248477) (#248538) # Backport This will backport the following commits from `main` to `9.3`: - [[Obs AI] `get_log_categories` tool: Rename `terms` to `kqlFilter` for consistency (#248477)](#248477) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Søren Louv-Jansen","email":"soren.louv@elastic.co"},"sourceCommit":{"committedDate":"2026-01-09T20:48:07Z","message":"[Obs AI] `get_log_categories` tool: Rename `terms` to `kqlFilter` for consistency (#248477)\n\nTools should use standardized terminology for the same operations.\n`kqlFilter` is now a common tool param across most of the o11y tools.\nThis renames `terms` param to `kqlFilter` param.\nThis also introduces `fields` param that enables the LLM to specify\nwhich fields should be returned in the response.","sha":"1ab14d0168d59f22e96499966a3640e48b3cdcab","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","v9.3.0","v9.4.0"],"title":"[Obs AI] `get_log_categories` tool: Rename `terms` to `kqlFilter` for consistency","number":248477,"url":"https://github.com/elastic/kibana/pull/248477","mergeCommit":{"message":"[Obs AI] `get_log_categories` tool: Rename `terms` to `kqlFilter` for consistency (#248477)\n\nTools should use standardized terminology for the same operations.\n`kqlFilter` is now a common tool param across most of the o11y tools.\nThis renames `terms` param to `kqlFilter` param.\nThis also introduces `fields` param that enables the LLM to specify\nwhich fields should be returned in the response.","sha":"1ab14d0168d59f22e96499966a3640e48b3cdcab"}},"sourceBranch":"main","suggestedTargetBranches":["9.3"],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/248477","number":248477,"mergeCommit":{"message":"[Obs AI] `get_log_categories` tool: Rename `terms` to `kqlFilter` for consistency (#248477)\n\nTools should use standardized terminology for the same operations.\n`kqlFilter` is now a common tool param across most of the o11y tools.\nThis renames `terms` param to `kqlFilter` param.\nThis also introduces `fields` param that enables the LLM to specify\nwhich fields should be returned in the response.","sha":"1ab14d0168d59f22e96499966a3640e48b3cdcab"}}]}] BACKPORT--> Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co>
devamanv
pushed a commit
to devamanv/kibana
that referenced
this pull request
Jan 12, 2026
… consistency (elastic#248477) Tools should use standardized terminology for the same operations. `kqlFilter` is now a common tool param across most of the o11y tools. This renames `terms` param to `kqlFilter` param. This also introduces `fields` param that enables the LLM to specify which fields should be returned in the response.
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
4 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.
Tools should use standardized terminology for the same operations.
kqlFilteris now a common tool param across most of the o11y tools. This renamestermsparam tokqlFilterparam.This also introduces
fieldsparam that enables the LLM to specify which fields should be returned in the response.