Tags: elastic/kibana
Tags
[9.3] [AI Connector][Inference endpoint] Creation: adaptive allocatio… …ns not set correctly on serverless (#251357) (#254585) # Backport This will backport the following commits from `main` to `9.3`: - [[AI Connector][Inference endpoint] Creation: adaptive allocations not set correctly on serverless (#251357)](#251357) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Saikat Sarkar","email":"132922331+saikatsarkar056@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-02-23T19:04:49Z","message":"[AI Connector][Inference endpoint] Creation: adaptive allocations not set correctly on serverless (#251357)\n\n## Summary\n\nFixes AI Connector inference endpoint creation failing on serverless\nwhen using the 'elasticsearch' provider with adaptive allocations\nenabled.\n\nThe issue was that `num_threads` and `num_allocations` were being sent\nin the `providerConfig` alongside `adaptive_allocations`, which causes a\nconflict since these properties cannot be set when adaptive allocations\nis enabled.\n\nThis PR updates the form serializer to exclude `num_threads` and\n`num_allocations` from the payload when adaptive allocations is\nconfigured.\n\n\n\nhttps://github.com/user-attachments/assets/5d4b42ff-db33-4f3a-ab70-b32fcccbc445\n\n\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- [x] [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- [x] 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- [x] 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### Release note\nFixes AI Connector creation on serverless failing when adaptive\nallocations is enabled with the ElasticSearch provider.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Melissa <melissa.alvarez@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"82dc85e41b82908e61c9afc0f9ab18dc4a734172","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Search","backport:version","v9.3.0","v9.4.0"],"title":"[AI Connector][Inference endpoint] Creation: adaptive allocations not set correctly on serverless","number":251357,"url":"https://github.com/elastic/kibana/pull/251357","mergeCommit":{"message":"[AI Connector][Inference endpoint] Creation: adaptive allocations not set correctly on serverless (#251357)\n\n## Summary\n\nFixes AI Connector inference endpoint creation failing on serverless\nwhen using the 'elasticsearch' provider with adaptive allocations\nenabled.\n\nThe issue was that `num_threads` and `num_allocations` were being sent\nin the `providerConfig` alongside `adaptive_allocations`, which causes a\nconflict since these properties cannot be set when adaptive allocations\nis enabled.\n\nThis PR updates the form serializer to exclude `num_threads` and\n`num_allocations` from the payload when adaptive allocations is\nconfigured.\n\n\n\nhttps://github.com/user-attachments/assets/5d4b42ff-db33-4f3a-ab70-b32fcccbc445\n\n\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- [x] [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- [x] 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- [x] 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### Release note\nFixes AI Connector creation on serverless failing when adaptive\nallocations is enabled with the ElasticSearch provider.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Melissa <melissa.alvarez@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"82dc85e41b82908e61c9afc0f9ab18dc4a734172"}},"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/251357","number":251357,"mergeCommit":{"message":"[AI Connector][Inference endpoint] Creation: adaptive allocations not set correctly on serverless (#251357)\n\n## Summary\n\nFixes AI Connector inference endpoint creation failing on serverless\nwhen using the 'elasticsearch' provider with adaptive allocations\nenabled.\n\nThe issue was that `num_threads` and `num_allocations` were being sent\nin the `providerConfig` alongside `adaptive_allocations`, which causes a\nconflict since these properties cannot be set when adaptive allocations\nis enabled.\n\nThis PR updates the form serializer to exclude `num_threads` and\n`num_allocations` from the payload when adaptive allocations is\nconfigured.\n\n\n\nhttps://github.com/user-attachments/assets/5d4b42ff-db33-4f3a-ab70-b32fcccbc445\n\n\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- [x] [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- [x] 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- [x] 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### Release note\nFixes AI Connector creation on serverless failing when adaptive\nallocations is enabled with the ElasticSearch provider.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Melissa <melissa.alvarez@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"82dc85e41b82908e61c9afc0f9ab18dc4a734172"}}]}] BACKPORT-->
[9.2] fix(apm): prevent trace sample title from wrapping vertically (#… …254536) (#254578) # Backport This will backport the following commits from `main` to `9.2`: - [fix(apm): prevent trace sample title from wrapping vertically (#254536)](#254536) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan L Smith","email":"nathan.smith@elastic.co"},"sourceCommit":{"committedDate":"2026-02-23T18:49:39Z","message":"fix(apm): prevent trace sample title from wrapping vertically (#254536)\n\n## Summary\n\nThe \"Trace sample\" heading in the APM transaction details view wraps\ncharacter-by-character at narrow viewports. The `EuiFlexItem` wrapping\nthe title has `grow={false}` but still defaults to `flex-shrink: 1`, so\nwhen the action buttons on the right consume most of the row width, CSS\ncrushes the title below its intrinsic text width.\n\nFix: add `flexShrink: 0` to the title's flex item so it never shrinks\nbelow its content size.\n\n\n| Before | After |\n| :----------: | :----------: |\n| <img width=\"958\" height=\"722\" alt=\"CleanShot 2026-02-23 at 10 14\n16@2x\"\nsrc=\"https://github.com/user-attachments/assets/56d7303e-22c4-4c41-9e3c-a4e9b3ac86e2\"\n/> | <img width=\"992\" height=\"656\" alt=\"CleanShot 2026-02-23 at 10 12\n22@2x\"\nsrc=\"https://github.com/user-attachments/assets/02e3b3af-fa89-4757-937a-e00bef034ab1\"\n/> |\n\n## Test plan\n\n- Manually verified in Kibana APM transactions view at narrow browser\nwidths — \"Trace sample\" stays on one line\n\n---------\n\nCo-authored-by: Cursor <cursoragent@cursor.com>","sha":"bd5153b71f0d4ecfdf0d73409a27dc3e366c4763","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:all-open","v9.4.0","Team:obs-presentation"],"title":"fix(apm): prevent trace sample title from wrapping vertically","number":254536,"url":"https://github.com/elastic/kibana/pull/254536","mergeCommit":{"message":"fix(apm): prevent trace sample title from wrapping vertically (#254536)\n\n## Summary\n\nThe \"Trace sample\" heading in the APM transaction details view wraps\ncharacter-by-character at narrow viewports. The `EuiFlexItem` wrapping\nthe title has `grow={false}` but still defaults to `flex-shrink: 1`, so\nwhen the action buttons on the right consume most of the row width, CSS\ncrushes the title below its intrinsic text width.\n\nFix: add `flexShrink: 0` to the title's flex item so it never shrinks\nbelow its content size.\n\n\n| Before | After |\n| :----------: | :----------: |\n| <img width=\"958\" height=\"722\" alt=\"CleanShot 2026-02-23 at 10 14\n16@2x\"\nsrc=\"https://github.com/user-attachments/assets/56d7303e-22c4-4c41-9e3c-a4e9b3ac86e2\"\n/> | <img width=\"992\" height=\"656\" alt=\"CleanShot 2026-02-23 at 10 12\n22@2x\"\nsrc=\"https://github.com/user-attachments/assets/02e3b3af-fa89-4757-937a-e00bef034ab1\"\n/> |\n\n## Test plan\n\n- Manually verified in Kibana APM transactions view at narrow browser\nwidths — \"Trace sample\" stays on one line\n\n---------\n\nCo-authored-by: Cursor <cursoragent@cursor.com>","sha":"bd5153b71f0d4ecfdf0d73409a27dc3e366c4763"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/254536","number":254536,"mergeCommit":{"message":"fix(apm): prevent trace sample title from wrapping vertically (#254536)\n\n## Summary\n\nThe \"Trace sample\" heading in the APM transaction details view wraps\ncharacter-by-character at narrow viewports. The `EuiFlexItem` wrapping\nthe title has `grow={false}` but still defaults to `flex-shrink: 1`, so\nwhen the action buttons on the right consume most of the row width, CSS\ncrushes the title below its intrinsic text width.\n\nFix: add `flexShrink: 0` to the title's flex item so it never shrinks\nbelow its content size.\n\n\n| Before | After |\n| :----------: | :----------: |\n| <img width=\"958\" height=\"722\" alt=\"CleanShot 2026-02-23 at 10 14\n16@2x\"\nsrc=\"https://github.com/user-attachments/assets/56d7303e-22c4-4c41-9e3c-a4e9b3ac86e2\"\n/> | <img width=\"992\" height=\"656\" alt=\"CleanShot 2026-02-23 at 10 12\n22@2x\"\nsrc=\"https://github.com/user-attachments/assets/02e3b3af-fa89-4757-937a-e00bef034ab1\"\n/> |\n\n## Test plan\n\n- Manually verified in Kibana APM transactions view at narrow browser\nwidths — \"Trace sample\" stays on one line\n\n---------\n\nCo-authored-by: Cursor <cursoragent@cursor.com>","sha":"bd5153b71f0d4ecfdf0d73409a27dc3e366c4763"}}]}] BACKPORT--> Co-authored-by: Nathan L Smith <nathan.smith@elastic.co> Co-authored-by: Cursor <cursoragent@cursor.com>
[8.19] API Keys: handle paging through more than 10,000 keys (#250826) ( #254575) # Backport This will backport the following commits from `main` to `8.19`: - [API Keys: handle paging through more than 10,000 keys (#250826)](#250826) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Larry Gregory","email":"larry.gregory@elastic.co"},"sourceCommit":{"committedDate":"2026-02-23T18:21:19Z","message":"API Keys: handle paging through more than 10,000 keys (#250826)\n\n## Summary\n\nThis pull request refactors API key management pagination to use\nElasticsearch's `search_after` cursor-based pagination instead of\ntraditional page indices. It updates the API, UI state, and tests to\nsupport this approach, so that the UI can accommodate clusters with more\nthan 10,000 API Keys.\n\nResolves https://github.com/elastic/kibana/issues/250625\n\n\n> [!IMPORTANT]\n> This results in a design tradeoff. The previous screen had pages of\nresults that users could click through: `Pages: 1, 2, 3, ..., 10`. The\nnew screen does not allow users to jump to an arbitrary page, because\nthat functionality is not possible when using cursor-based pagination.\n\n\n<img width=\"1375\" height=\"1322\" alt=\"Larry Gregory 2026-02-11 at 10 43\n09\"\nsrc=\"https://github.com/user-attachments/assets/e041995b-e342-4a62-851e-5ff11116585c\"\n/>","sha":"6cb0bbf16bf4ca6f2e6b4b2491a97aa2a7084a28","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Security","Feature:Users/Roles/API Keys","backport:version","v9.4.0","v9.3.1","v8.19.12"],"title":"API Keys: handle paging through more than 10,000 keys","number":250826,"url":"https://github.com/elastic/kibana/pull/250826","mergeCommit":{"message":"API Keys: handle paging through more than 10,000 keys (#250826)\n\n## Summary\n\nThis pull request refactors API key management pagination to use\nElasticsearch's `search_after` cursor-based pagination instead of\ntraditional page indices. It updates the API, UI state, and tests to\nsupport this approach, so that the UI can accommodate clusters with more\nthan 10,000 API Keys.\n\nResolves https://github.com/elastic/kibana/issues/250625\n\n\n> [!IMPORTANT]\n> This results in a design tradeoff. The previous screen had pages of\nresults that users could click through: `Pages: 1, 2, 3, ..., 10`. The\nnew screen does not allow users to jump to an arbitrary page, because\nthat functionality is not possible when using cursor-based pagination.\n\n\n<img width=\"1375\" height=\"1322\" alt=\"Larry Gregory 2026-02-11 at 10 43\n09\"\nsrc=\"https://github.com/user-attachments/assets/e041995b-e342-4a62-851e-5ff11116585c\"\n/>","sha":"6cb0bbf16bf4ca6f2e6b4b2491a97aa2a7084a28"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/250826","number":250826,"mergeCommit":{"message":"API Keys: handle paging through more than 10,000 keys (#250826)\n\n## Summary\n\nThis pull request refactors API key management pagination to use\nElasticsearch's `search_after` cursor-based pagination instead of\ntraditional page indices. It updates the API, UI state, and tests to\nsupport this approach, so that the UI can accommodate clusters with more\nthan 10,000 API Keys.\n\nResolves https://github.com/elastic/kibana/issues/250625\n\n\n> [!IMPORTANT]\n> This results in a design tradeoff. The previous screen had pages of\nresults that users could click through: `Pages: 1, 2, 3, ..., 10`. The\nnew screen does not allow users to jump to an arbitrary page, because\nthat functionality is not possible when using cursor-based pagination.\n\n\n<img width=\"1375\" height=\"1322\" alt=\"Larry Gregory 2026-02-11 at 10 43\n09\"\nsrc=\"https://github.com/user-attachments/assets/e041995b-e342-4a62-851e-5ff11116585c\"\n/>","sha":"6cb0bbf16bf4ca6f2e6b4b2491a97aa2a7084a28"}},{"branch":"9.3","label":"v9.3.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/254572","number":254572,"state":"OPEN"},{"branch":"8.19","label":"v8.19.12","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
Reverting the wolfi images to glibc-2.42 (#254562)
[9.3] [Obs AI] Update AI Insight UI description (#250137) (#250248) # Backport This will backport the following commits from `main` to `9.3`: - [[Obs AI] Update AI Insight UI description (#250137)](#250137) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Viduni Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2026-01-23T15:55:06Z","message":"[Obs AI] Update AI Insight UI description (#250137)\n\nCloses https://github.com/elastic/obs-ai-team/issues/480\n\n## Summary\n\nAI Insights use the Observability Agent with the merge of\nhttps://github.com//pull/249776\n\nThis PR updates the AI Insight subtitle copy to say `Observability\nAgent` instead of `Elastic AI Agent` .\n\n<img width=\"1344\" height=\"96\" alt=\"Screenshot 2026-01-22 at 7 37 39 PM\"\nsrc=\"https://github.com/user-attachments/assets/a6e5e669-ac8d-4008-9f49-316c677b1de9\"\n/>\n\n### Checklist\n\n- [x] 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- [x] 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- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"81b759e4fbf82007ceb47924dcea52e9065f19e7","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:version","Team:obs-ai","v9.4.0","v9.3.1"],"title":"[Obs AI] Update AI Insight UI description","number":250137,"url":"https://github.com/elastic/kibana/pull/250137","mergeCommit":{"message":"[Obs AI] Update AI Insight UI description (#250137)\n\nCloses https://github.com/elastic/obs-ai-team/issues/480\n\n## Summary\n\nAI Insights use the Observability Agent with the merge of\nhttps://github.com//pull/249776\n\nThis PR updates the AI Insight subtitle copy to say `Observability\nAgent` instead of `Elastic AI Agent` .\n\n<img width=\"1344\" height=\"96\" alt=\"Screenshot 2026-01-22 at 7 37 39 PM\"\nsrc=\"https://github.com/user-attachments/assets/a6e5e669-ac8d-4008-9f49-316c677b1de9\"\n/>\n\n### Checklist\n\n- [x] 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- [x] 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- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"81b759e4fbf82007ceb47924dcea52e9065f19e7"}},"sourceBranch":"main","suggestedTargetBranches":["9.3"],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/250137","number":250137,"mergeCommit":{"message":"[Obs AI] Update AI Insight UI description (#250137)\n\nCloses https://github.com/elastic/obs-ai-team/issues/480\n\n## Summary\n\nAI Insights use the Observability Agent with the merge of\nhttps://github.com//pull/249776\n\nThis PR updates the AI Insight subtitle copy to say `Observability\nAgent` instead of `Elastic AI Agent` .\n\n<img width=\"1344\" height=\"96\" alt=\"Screenshot 2026-01-22 at 7 37 39 PM\"\nsrc=\"https://github.com/user-attachments/assets/a6e5e669-ac8d-4008-9f49-316c677b1de9\"\n/>\n\n### Checklist\n\n- [x] 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- [x] 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- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"81b759e4fbf82007ceb47924dcea52e9065f19e7"}},{"branch":"9.3","label":"v9.3.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co>
PreviousNext