Commit 41a47a2
Closes elastic/obs-ai-team#380
# Backport
This will backport the following commits from `main` to `9.2`:
- [[Obs AI Assistant] aware of new .integration_knowledge* system index
(#237085)](#237085)
<!--- Backport version: 10.0.2 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)
<!--BACKPORT [{"author":{"name":"Arturo
Lidueña","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-10-14T07:13:31Z","message":"[Obs
AI Assistant] aware of new .integration_knowledge* system index
(#237085)\n\nCloses
https://github.com/elastic/obs-ai-assistant-team/issues/357\n##
Summary\n\nThis PR adds the awareness of `.integration_knowledge*` index
as another\nindex for recalling. The Obs AI Assistant will retrieve
integration\nknowledge from the index\n\nValue added to the Obs AI
Assistant\n(https://github.com/elastic/obs-ai-assistant-team/issues/357#issuecomment-3303692842):\n>
The assistant will become aware of LLM-facing documentation for
any\ninstalled integrations in the user's cluster. For example, the
Logstash\nintegration might ship documentation that explains how to
understand the\nhealth reporting metrics collected by the integration
and the assistant\ncould answer prompts like \"why was my logstash
server down yesterday?\"\nusing the user's real data.\n\nManual Testing:
\n1 -> Follow the instructions
from\nhttps://github.com//pull/230107#issue-3281157774:\n\n>
1. If elastic/elasticsearch#132506 has
been\nmerged, run `yarn es snapshot` in Kibana, otherwise, checkout
that\nbranch in your local ES and then in kibana run `yarn es source` in
order\nto use that version of ES which contains the index management,
mappings,\netc.\n>2. Install a package with any number of knowledge base
docs in the\n`docs/knowledge_base` folder. You can use [this
sample\npackage](https://github.com/user-attachments/files/21867395/masonstestpackage-0.0.1.zip),\nor
create your own following the guide below:\n>\n> - Using
`elastic-package`, create a new package using `elastic-package\ncreate
integration`\n- Once created add `knowledge_base` as a folder inside of
the generated\n`docs` folder of the integration\n- Add an arbitrary
amount of `.md` files to the knowledge_base folder\n - Run
`elastic-package build` to build the package\n- There are a lot of
different options for installing the package in a\nlocal kibana
instance. I prefer to just take the generated .zip folder\nfrom `/build`
in `elastic-package` and upload it to kibana using the\ncustom
integrations feature. You can also expose the package registry,\nor
whatever you see fit.\n>3. Watch the Kibana logs for errors/debug
messages etc\n>4. Use the new endpoint or just directly check the index
using `GET\n/.integration_knowledge/_search` to verify that the
documents are\ningested into the system index of
`.integration_knowledge`\n>5. Update the package and verify that the KB
documents are updated by\nchecking the response again, they should have
the updated pkgVersion on\nthe associated docs.\n>6. Remove the package
and then verify (using the endpoint) that the\ndocs are removed from the
index\n\n2 - Ask the AI Assistant about information contained in the
integration\ndocuments\n\n3- check that the documents are listed on the
response of executed the\nfunction context inside learnings\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: kibanamachine
<[email protected]>\nCo-authored-by:
Sandra G
<[email protected]>","sha":"15878ad8a124539d4698de2510fd5d6ad90b8d38","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","backport:skip","Team:Obs
AI Assistant","ci:project-deploy-observability","v9.3.0"],"title":"[Obs
AI Assistant] aware of new .integration_knowledge* system
index","number":237085,"url":"https://github.com/elastic/kibana/pull/237085","mergeCommit":{"message":"[Obs
AI Assistant] aware of new .integration_knowledge* system index
(#237085)\n\nCloses
https://github.com/elastic/obs-ai-assistant-team/issues/357\n##
Summary\n\nThis PR adds the awareness of `.integration_knowledge*` index
as another\nindex for recalling. The Obs AI Assistant will retrieve
integration\nknowledge from the index\n\nValue added to the Obs AI
Assistant\n(https://github.com/elastic/obs-ai-assistant-team/issues/357#issuecomment-3303692842):\n>
The assistant will become aware of LLM-facing documentation for
any\ninstalled integrations in the user's cluster. For example, the
Logstash\nintegration might ship documentation that explains how to
understand the\nhealth reporting metrics collected by the integration
and the assistant\ncould answer prompts like \"why was my logstash
server down yesterday?\"\nusing the user's real data.\n\nManual Testing:
\n1 -> Follow the instructions
from\nhttps://github.com//pull/230107#issue-3281157774:\n\n>
1. If elastic/elasticsearch#132506 has
been\nmerged, run `yarn es snapshot` in Kibana, otherwise, checkout
that\nbranch in your local ES and then in kibana run `yarn es source` in
order\nto use that version of ES which contains the index management,
mappings,\netc.\n>2. Install a package with any number of knowledge base
docs in the\n`docs/knowledge_base` folder. You can use [this
sample\npackage](https://github.com/user-attachments/files/21867395/masonstestpackage-0.0.1.zip),\nor
create your own following the guide below:\n>\n> - Using
`elastic-package`, create a new package using `elastic-package\ncreate
integration`\n- Once created add `knowledge_base` as a folder inside of
the generated\n`docs` folder of the integration\n- Add an arbitrary
amount of `.md` files to the knowledge_base folder\n - Run
`elastic-package build` to build the package\n- There are a lot of
different options for installing the package in a\nlocal kibana
instance. I prefer to just take the generated .zip folder\nfrom `/build`
in `elastic-package` and upload it to kibana using the\ncustom
integrations feature. You can also expose the package registry,\nor
whatever you see fit.\n>3. Watch the Kibana logs for errors/debug
messages etc\n>4. Use the new endpoint or just directly check the index
using `GET\n/.integration_knowledge/_search` to verify that the
documents are\ningested into the system index of
`.integration_knowledge`\n>5. Update the package and verify that the KB
documents are updated by\nchecking the response again, they should have
the updated pkgVersion on\nthe associated docs.\n>6. Remove the package
and then verify (using the endpoint) that the\ndocs are removed from the
index\n\n2 - Ask the AI Assistant about information contained in the
integration\ndocuments\n\n3- check that the documents are listed on the
response of executed the\nfunction context inside learnings\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: kibanamachine
<[email protected]>\nCo-authored-by:
Sandra G
<[email protected]>","sha":"15878ad8a124539d4698de2510fd5d6ad90b8d38"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/237085","number":237085,"mergeCommit":{"message":"[Obs
AI Assistant] aware of new .integration_knowledge* system index
(#237085)\n\nCloses
https://github.com/elastic/obs-ai-assistant-team/issues/357\n##
Summary\n\nThis PR adds the awareness of `.integration_knowledge*` index
as another\nindex for recalling. The Obs AI Assistant will retrieve
integration\nknowledge from the index\n\nValue added to the Obs AI
Assistant\n(https://github.com/elastic/obs-ai-assistant-team/issues/357#issuecomment-3303692842):\n>
The assistant will become aware of LLM-facing documentation for
any\ninstalled integrations in the user's cluster. For example, the
Logstash\nintegration might ship documentation that explains how to
understand the\nhealth reporting metrics collected by the integration
and the assistant\ncould answer prompts like \"why was my logstash
server down yesterday?\"\nusing the user's real data.\n\nManual Testing:
\n1 -> Follow the instructions
from\nhttps://github.com//pull/230107#issue-3281157774:\n\n>
1. If elastic/elasticsearch#132506 has
been\nmerged, run `yarn es snapshot` in Kibana, otherwise, checkout
that\nbranch in your local ES and then in kibana run `yarn es source` in
order\nto use that version of ES which contains the index management,
mappings,\netc.\n>2. Install a package with any number of knowledge base
docs in the\n`docs/knowledge_base` folder. You can use [this
sample\npackage](https://github.com/user-attachments/files/21867395/masonstestpackage-0.0.1.zip),\nor
create your own following the guide below:\n>\n> - Using
`elastic-package`, create a new package using `elastic-package\ncreate
integration`\n- Once created add `knowledge_base` as a folder inside of
the generated\n`docs` folder of the integration\n- Add an arbitrary
amount of `.md` files to the knowledge_base folder\n - Run
`elastic-package build` to build the package\n- There are a lot of
different options for installing the package in a\nlocal kibana
instance. I prefer to just take the generated .zip folder\nfrom `/build`
in `elastic-package` and upload it to kibana using the\ncustom
integrations feature. You can also expose the package registry,\nor
whatever you see fit.\n>3. Watch the Kibana logs for errors/debug
messages etc\n>4. Use the new endpoint or just directly check the index
using `GET\n/.integration_knowledge/_search` to verify that the
documents are\ningested into the system index of
`.integration_knowledge`\n>5. Update the package and verify that the KB
documents are updated by\nchecking the response again, they should have
the updated pkgVersion on\nthe associated docs.\n>6. Remove the package
and then verify (using the endpoint) that the\ndocs are removed from the
index\n\n2 - Ask the AI Assistant about information contained in the
integration\ndocuments\n\n3- check that the documents are listed on the
response of executed the\nfunction context inside learnings\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: kibanamachine
<[email protected]>\nCo-authored-by:
Sandra G
<[email protected]>","sha":"15878ad8a124539d4698de2510fd5d6ad90b8d38"}}]}]
BACKPORT-->
---------
Co-authored-by: kibanamachine <[email protected]>
Co-authored-by: Sandra G <[email protected]>
Co-authored-by: Viduni Wickramarachchi <[email protected]>
1 parent 0753e91 commit 41a47a2
File tree
2 files changed
+114
-26
lines changed2 files changed
+114
-26
lines changedLines changed: 9 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
205 | 205 | | |
206 | 206 | | |
207 | 207 | | |
| 208 | + | |
| 209 | + | |
| 210 | + | |
| 211 | + | |
| 212 | + | |
| 213 | + | |
| 214 | + | |
| 215 | + | |
| 216 | + | |
Lines changed: 105 additions & 26 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
13 | 13 | | |
14 | 14 | | |
15 | 15 | | |
16 | | - | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
17 | 21 | | |
18 | 22 | | |
19 | 23 | | |
| |||
36 | 40 | | |
37 | 41 | | |
38 | 42 | | |
| 43 | + | |
| 44 | + | |
39 | 45 | | |
40 | 46 | | |
41 | 47 | | |
| |||
112 | 118 | | |
113 | 119 | | |
114 | 120 | | |
| 121 | + | |
| 122 | + | |
| 123 | + | |
| 124 | + | |
| 125 | + | |
| 126 | + | |
| 127 | + | |
| 128 | + | |
| 129 | + | |
| 130 | + | |
| 131 | + | |
| 132 | + | |
| 133 | + | |
| 134 | + | |
| 135 | + | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
| 139 | + | |
| 140 | + | |
| 141 | + | |
| 142 | + | |
| 143 | + | |
| 144 | + | |
| 145 | + | |
| 146 | + | |
| 147 | + | |
| 148 | + | |
| 149 | + | |
| 150 | + | |
| 151 | + | |
| 152 | + | |
| 153 | + | |
| 154 | + | |
| 155 | + | |
| 156 | + | |
| 157 | + | |
| 158 | + | |
| 159 | + | |
| 160 | + | |
| 161 | + | |
| 162 | + | |
| 163 | + | |
| 164 | + | |
| 165 | + | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
| 170 | + | |
| 171 | + | |
| 172 | + | |
| 173 | + | |
| 174 | + | |
| 175 | + | |
| 176 | + | |
| 177 | + | |
| 178 | + | |
115 | 179 | | |
116 | 180 | | |
117 | 181 | | |
| |||
137 | 201 | | |
138 | 202 | | |
139 | 203 | | |
140 | | - | |
141 | | - | |
142 | | - | |
143 | | - | |
144 | | - | |
145 | | - | |
146 | | - | |
147 | | - | |
148 | | - | |
149 | | - | |
150 | | - | |
151 | | - | |
152 | | - | |
153 | | - | |
154 | | - | |
155 | | - | |
156 | | - | |
157 | | - | |
158 | | - | |
159 | | - | |
160 | | - | |
161 | | - | |
162 | | - | |
163 | | - | |
| 204 | + | |
| 205 | + | |
| 206 | + | |
| 207 | + | |
| 208 | + | |
| 209 | + | |
| 210 | + | |
| 211 | + | |
| 212 | + | |
| 213 | + | |
| 214 | + | |
| 215 | + | |
| 216 | + | |
| 217 | + | |
| 218 | + | |
| 219 | + | |
| 220 | + | |
| 221 | + | |
| 222 | + | |
| 223 | + | |
| 224 | + | |
| 225 | + | |
| 226 | + | |
| 227 | + | |
| 228 | + | |
| 229 | + | |
| 230 | + | |
| 231 | + | |
| 232 | + | |
| 233 | + | |
| 234 | + | |
| 235 | + | |
| 236 | + | |
| 237 | + | |
| 238 | + | |
| 239 | + | |
164 | 240 | | |
165 | 241 | | |
166 | 242 | | |
167 | 243 | | |
168 | 244 | | |
169 | 245 | | |
170 | 246 | | |
| 247 | + | |
| 248 | + | |
| 249 | + | |
171 | 250 | | |
172 | 251 | | |
173 | | - | |
| 252 | + | |
174 | 253 | | |
175 | 254 | | |
176 | 255 | | |
| |||
0 commit comments