github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 01:13:23 -04:00
Code Issues Projects Releases Packages Wiki Activity
83042 commits 431 branches 496 tags 22 GiB
Commit graph

564 commits

Author SHA1 Message Date
Larry Gregory
24f82ee808
[8.x] Additional prototype pollution protections (#206073) (#208742) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Additional prototype pollution protections
(#206073)](https://github.com/elastic/kibana/pull/206073)

<!--- Backport version: 9.6.4 -->

### 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":"2025-01-28T22:00:43Z","message":"Additional
prototype pollution protections (#206073)\n\n## Summary\n\n1. Extends
the server-side prototype pollution protections introduced
in\nhttps://github.com/elastic/kibana/pull/190716 to
include\n`Array.prototype`.\n2. Applies the same prototype pollution
protections to the client-side.\n\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- [ ]
Sealing prototypes on the client can lead to failures in\nthird-party
dependencies. I'm relying on sufficient functional test\ncoverage to
detect issues here. As a result, these protections are\ndisabled by
default for now, and can be controlled via
setting\n`server.prototypeHardening:
true/false`\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"9ce2dd8df9f2bd6c0ba1d089b69ddfd7fc1f4a02","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","Feature:Hardening","v9.0.0","backport:prev-minor","ci:cloud-deploy","ci:project-deploy-elasticsearch","ci:all-gen-ai-suites"],"title":"Additional
prototype pollution
protections","number":206073,"url":"https://github.com/elastic/kibana/pull/206073","mergeCommit":{"message":"Additional
prototype pollution protections (#206073)\n\n## Summary\n\n1. Extends
the server-side prototype pollution protections introduced
in\nhttps://github.com/elastic/kibana/pull/190716 to
include\n`Array.prototype`.\n2. Applies the same prototype pollution
protections to the client-side.\n\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- [ ]
Sealing prototypes on the client can lead to failures in\nthird-party
dependencies. I'm relying on sufficient functional test\ncoverage to
detect issues here. As a result, these protections are\ndisabled by
default for now, and can be controlled via
setting\n`server.prototypeHardening:
true/false`\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"9ce2dd8df9f2bd6c0ba1d089b69ddfd7fc1f4a02"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206073","number":206073,"mergeCommit":{"message":"Additional
prototype pollution protections (#206073)\n\n## Summary\n\n1. Extends
the server-side prototype pollution protections introduced
in\nhttps://github.com/elastic/kibana/pull/190716 to
include\n`Array.prototype`.\n2. Applies the same prototype pollution
protections to the client-side.\n\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- [ ]
Sealing prototypes on the client can lead to failures in\nthird-party
dependencies. I'm relying on sufficient functional test\ncoverage to
detect issues here. As a result, these protections are\ndisabled by
default for now, and can be controlled via
setting\n`server.prototypeHardening:
true/false`\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"9ce2dd8df9f2bd6c0ba1d089b69ddfd7fc1f4a02"}}]}]
BACKPORT-->
 2025-01-29 15:08:04 -05:00
Nathan Reese
c39e129298
[8.x] [embeddable] make presentation interface names consistent (#205279) (#207881) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[embeddable] make presentation interface names consistent
(#205279)](https://github.com/elastic/kibana/pull/205279)

<!--- Backport version: 9.6.4 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Nathan
Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T16:46:01Z","message":"[embeddable]
make presentation interface names consistent (#205279)\n\nPR cleans up
presentation interface names for consistentency\r\n* adds `# Backport

This will backport the following commits from `main` to `8.x`:
- [[embeddable] make presentation interface names consistent
(#205279)](https://github.com/elastic/kibana/pull/205279)

<!--- Backport version: 9.6.4 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT suffix to all observables. For example, `dataLoading`
=>\r\n`dataLoading# Backport

This will backport the following commits from `main` to `8.x`:
- [[embeddable] make presentation interface names consistent
(#205279)](https://github.com/elastic/kibana/pull/205279)

<!--- Backport version: 9.6.4 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT \r\n* removes `Panel` naming convention from interface
names since an api\r\nmay not be a panel, an api may be a dashboard. For
example,\r\n`PublisesPanelTitle` => `PublishesTitle`\r\n\r\n#### Note to
Reviewers\r\nPay special attention to any place where your application
creates an\r\nuntyped API. In the example below, there is no typescript
violation when\r\nthe parent returns `dataLoading` instead of
`dataLoading# Backport

This will backport the following commits from `main` to `8.x`:
- [[embeddable] make presentation interface names consistent
(#205279)](https://github.com/elastic/kibana/pull/205279)

<!--- Backport version: 9.6.4 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT since the\r\nparent is not typed as `PublishesDataLoading`.
Please check for\r\ninstances like
these.\r\n\r\n```\r\n<ReactEmbeddableRenderer\r\n getParentApi={() =>
{\r\n dataLoading: new BehaviorSubject()\r\n
}}\r\n/>\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"05916056cdc84c0f59392046aa4ffc7d16e083f9","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Embedding","Team:Presentation","release_note:skip","Feature:Drilldowns","v9.0.0","Team:obs-ux-infra_services","Team:obs-ux-management","project:embeddableRebuild","backport:version","v8.18.0"],"title":"[embeddable]
make presentation interface names
consistent","number":205279,"url":"https://github.com/elastic/kibana/pull/205279","mergeCommit":{"message":"[embeddable]
make presentation interface names consistent (#205279)\n\nPR cleans up
presentation interface names for consistentency\r\n* adds `# Backport

This will backport the following commits from `main` to `8.x`:
- [[embeddable] make presentation interface names consistent
(#205279)](https://github.com/elastic/kibana/pull/205279)

<!--- Backport version: 9.6.4 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT suffix to all observables. For example, `dataLoading`
=>\r\n`dataLoading# Backport

This will backport the following commits from `main` to `8.x`:
- [[embeddable] make presentation interface names consistent
(#205279)](https://github.com/elastic/kibana/pull/205279)

<!--- Backport version: 9.6.4 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT \r\n* removes `Panel` naming convention from interface
names since an api\r\nmay not be a panel, an api may be a dashboard. For
example,\r\n`PublisesPanelTitle` => `PublishesTitle`\r\n\r\n#### Note to
Reviewers\r\nPay special attention to any place where your application
creates an\r\nuntyped API. In the example below, there is no typescript
violation when\r\nthe parent returns `dataLoading` instead of
`dataLoading# Backport

This will backport the following commits from `main` to `8.x`:
- [[embeddable] make presentation interface names consistent
(#205279)](https://github.com/elastic/kibana/pull/205279)

<!--- Backport version: 9.6.4 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT since the\r\nparent is not typed as `PublishesDataLoading`.
Please check for\r\ninstances like
these.\r\n\r\n```\r\n<ReactEmbeddableRenderer\r\n getParentApi={() =>
{\r\n dataLoading: new BehaviorSubject()\r\n
}}\r\n/>\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"05916056cdc84c0f59392046aa4ffc7d16e083f9"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205279","number":205279,"mergeCommit":{"message":"[embeddable]
make presentation interface names consistent (#205279)\n\nPR cleans up
presentation interface names for consistentency\r\n* adds `# Backport

This will backport the following commits from `main` to `8.x`:
- [[embeddable] make presentation interface names consistent
(#205279)](https://github.com/elastic/kibana/pull/205279)

<!--- Backport version: 9.6.4 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT suffix to all observables. For example, `dataLoading`
=>\r\n`dataLoading# Backport

This will backport the following commits from `main` to `8.x`:
- [[embeddable] make presentation interface names consistent
(#205279)](https://github.com/elastic/kibana/pull/205279)

<!--- Backport version: 9.6.4 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT \r\n* removes `Panel` naming convention from interface
names since an api\r\nmay not be a panel, an api may be a dashboard. For
example,\r\n`PublisesPanelTitle` => `PublishesTitle`\r\n\r\n#### Note to
Reviewers\r\nPay special attention to any place where your application
creates an\r\nuntyped API. In the example below, there is no typescript
violation when\r\nthe parent returns `dataLoading` instead of
`dataLoading# Backport

This will backport the following commits from `main` to `8.x`:
- [[embeddable] make presentation interface names consistent
(#205279)](https://github.com/elastic/kibana/pull/205279)

<!--- Backport version: 9.6.4 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT since the\r\nparent is not typed as `PublishesDataLoading`.
Please check for\r\ninstances like
these.\r\n\r\n```\r\n<ReactEmbeddableRenderer\r\n getParentApi={() =>
{\r\n dataLoading: new BehaviorSubject()\r\n
}}\r\n/>\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"05916056cdc84c0f59392046aa4ffc7d16e083f9"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-01-22 18:26:52 +00:00
Michael Dokolin
861c2de3e5
[8.x] Sustainable Kibana Architecture: Move modules owned by @elastic/kibana-core (#201653) (#205563) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Sustainable Kibana Architecture: Move modules owned by
`@elastic/kibana-core`
(#201653)](https://github.com/elastic/kibana/pull/201653)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Gerard
Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-01-04T18:47:24Z","message":"Sustainable
Kibana Architecture: Move modules owned by `@elastic/kibana-core`
(#201653)\n\n## Summary\n\nStart relocating Kibana modules (packages and
plugins) to the new folder\nstructure, according to the _Kibana
Sustainable Architecture_\ninitiative.\n#### 16 plugin(s) are going to
be relocated:\n\n| Id | Target folder |\n| -- | ------------- |\n|
`@kbn/cloud-chat-plugin`
|\n`x-pack/platform/plugins/private/cloud_integrations/cloud_chat` |\n|
`@kbn/cloud-experiments-plugin`
|\n`x-pack/platform/plugins/shared/cloud_integrations/cloud_experiments`
|\n| `@kbn/cloud-full-story-plugin`
|\n`x-pack/platform/plugins/private/cloud_integrations/cloud_full_story`
|\n| `@kbn/cloud-links-plugin`
|\n`x-pack/platform/plugins/private/cloud_integrations/cloud_links` |\n|
`@kbn/cloud-plugin` | `x-pack/platform/plugins/shared/cloud` |\n|
`@kbn/features-plugin` | `x-pack/platform/plugins/shared/features` |\n|
`@kbn/ftr-apis-plugin` | `src/platform/plugins/private/ftr_apis` |\n|
`@kbn/kibana-usage-collection-plugin`
|\n`src/platform/plugins/private/kibana_usage_collection` |\n|
`@kbn/licensing-plugin` | `x-pack/platform/plugins/shared/licensing`
|\n| `@kbn/newsfeed-plugin` | `src/platform/plugins/shared/newsfeed`
|\n| `@kbn/saved-objects-management-plugin`
|\n`src/platform/plugins/shared/saved_objects_management` |\n|
`@kbn/telemetry-collection-manager-plugin`
|\n`src/platform/plugins/shared/telemetry_collection_manager` |\n|
`@kbn/telemetry-collection-xpack-plugin`
|\n`x-pack/platform/plugins/private/telemetry_collection_xpack` |\n|
`@kbn/telemetry-management-section-plugin`
|\n`src/platform/plugins/shared/telemetry_management_section` |\n|
`@kbn/telemetry-plugin` | `src/platform/plugins/shared/telemetry` |\n|
`@kbn/usage-collection-plugin`
|\n`src/platform/plugins/shared/usage_collection` |\n\n#### 22
package(s) are going to be relocated:\n\n| Id | Target folder |\n| -- |
------------- |\n| `@kbn/analytics` |
`src/platform/packages/shared/kbn-analytics` |\n|
`@kbn/analytics-collection-utils`
|\n`src/platform/packages/private/analytics/utils/analytics_collection_utils`\n|\n|
`@kbn/apm-config-loader`
|\n`src/platform/packages/private/kbn-apm-config-loader` |\n|
`@kbn/cloud` | `src/platform/packages/shared/cloud` |\n| `@kbn/config` |
`src/platform/packages/shared/kbn-config` |\n| `@kbn/config-mocks` |
`src/platform/packages/private/kbn-config-mocks`\n|\n|
`@kbn/config-schema` |\n`src/platform/packages/shared/kbn-config-schema`
|\n| `@kbn/crypto-browser`
|\n`src/platform/packages/shared/kbn-crypto-browser` |\n|
`@kbn/ebt-tools` | `src/platform/packages/shared/kbn-ebt-tools` |\n|
`@kbn/es-errors` | `src/platform/packages/shared/kbn-es-errors` |\n|
`@kbn/es-types` | `src/platform/packages/shared/kbn-es-types` |\n|
`@kbn/hapi-mocks` | `src/platform/packages/private/kbn-hapi-mocks` |\n|
`@kbn/health-gateway-server`
|\n`src/platform/packages/private/kbn-health-gateway-server` |\n|
`@kbn/i18n` | `src/platform/packages/shared/kbn-i18n` |\n|
`@kbn/i18n-react` | `src/platform/packages/shared/kbn-i18n-react` |\n|
`@kbn/logging` | `src/platform/packages/shared/kbn-logging` |\n|
`@kbn/logging-mocks` |\n`src/platform/packages/shared/kbn-logging-mocks`
|\n| `@kbn/router-to-openapispec`
|\n`src/platform/packages/shared/kbn-router-to-openapispec` |\n|
`@kbn/server-http-tools`
|\n`src/platform/packages/shared/kbn-server-http-tools` |\n| `@kbn/std`
| `src/platform/packages/shared/kbn-std` |\n| `@kbn/utility-types`
|\n`src/platform/packages/shared/kbn-utility-types` |\n| `@kbn/zod` |
`src/platform/packages/shared/kbn-zod` |\n\n---------\n\nCo-authored-by:
Alejandro Fernández Haro <alejandro.haro@elastic.co>\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"6049493e4a2372ea22986b231ad2bd59584fe9b8","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","plugin
groups"],"number":201653,"url":"https://github.com/elastic/kibana/pull/201653","mergeCommit":{"message":"Sustainable
Kibana Architecture: Move modules owned by `@elastic/kibana-core`
(#201653)\n\n## Summary\n\nStart relocating Kibana modules (packages and
plugins) to the new folder\nstructure, according to the _Kibana
Sustainable Architecture_\ninitiative.\n#### 16 plugin(s) are going to
be relocated:\n\n| Id | Target folder |\n| -- | ------------- |\n|
`@kbn/cloud-chat-plugin`
|\n`x-pack/platform/plugins/private/cloud_integrations/cloud_chat` |\n|
`@kbn/cloud-experiments-plugin`
|\n`x-pack/platform/plugins/shared/cloud_integrations/cloud_experiments`
|\n| `@kbn/cloud-full-story-plugin`
|\n`x-pack/platform/plugins/private/cloud_integrations/cloud_full_story`
|\n| `@kbn/cloud-links-plugin`
|\n`x-pack/platform/plugins/private/cloud_integrations/cloud_links` |\n|
`@kbn/cloud-plugin` | `x-pack/platform/plugins/shared/cloud` |\n|
`@kbn/features-plugin` | `x-pack/platform/plugins/shared/features` |\n|
`@kbn/ftr-apis-plugin` | `src/platform/plugins/private/ftr_apis` |\n|
`@kbn/kibana-usage-collection-plugin`
|\n`src/platform/plugins/private/kibana_usage_collection` |\n|
`@kbn/licensing-plugin` | `x-pack/platform/plugins/shared/licensing`
|\n| `@kbn/newsfeed-plugin` | `src/platform/plugins/shared/newsfeed`
|\n| `@kbn/saved-objects-management-plugin`
|\n`src/platform/plugins/shared/saved_objects_management` |\n|
`@kbn/telemetry-collection-manager-plugin`
|\n`src/platform/plugins/shared/telemetry_collection_manager` |\n|
`@kbn/telemetry-collection-xpack-plugin`
|\n`x-pack/platform/plugins/private/telemetry_collection_xpack` |\n|
`@kbn/telemetry-management-section-plugin`
|\n`src/platform/plugins/shared/telemetry_management_section` |\n|
`@kbn/telemetry-plugin` | `src/platform/plugins/shared/telemetry` |\n|
`@kbn/usage-collection-plugin`
|\n`src/platform/plugins/shared/usage_collection` |\n\n#### 22
package(s) are going to be relocated:\n\n| Id | Target folder |\n| -- |
------------- |\n| `@kbn/analytics` |
`src/platform/packages/shared/kbn-analytics` |\n|
`@kbn/analytics-collection-utils`
|\n`src/platform/packages/private/analytics/utils/analytics_collection_utils`\n|\n|
`@kbn/apm-config-loader`
|\n`src/platform/packages/private/kbn-apm-config-loader` |\n|
`@kbn/cloud` | `src/platform/packages/shared/cloud` |\n| `@kbn/config` |
`src/platform/packages/shared/kbn-config` |\n| `@kbn/config-mocks` |
`src/platform/packages/private/kbn-config-mocks`\n|\n|
`@kbn/config-schema` |\n`src/platform/packages/shared/kbn-config-schema`
|\n| `@kbn/crypto-browser`
|\n`src/platform/packages/shared/kbn-crypto-browser` |\n|
`@kbn/ebt-tools` | `src/platform/packages/shared/kbn-ebt-tools` |\n|
`@kbn/es-errors` | `src/platform/packages/shared/kbn-es-errors` |\n|
`@kbn/es-types` | `src/platform/packages/shared/kbn-es-types` |\n|
`@kbn/hapi-mocks` | `src/platform/packages/private/kbn-hapi-mocks` |\n|
`@kbn/health-gateway-server`
|\n`src/platform/packages/private/kbn-health-gateway-server` |\n|
`@kbn/i18n` | `src/platform/packages/shared/kbn-i18n` |\n|
`@kbn/i18n-react` | `src/platform/packages/shared/kbn-i18n-react` |\n|
`@kbn/logging` | `src/platform/packages/shared/kbn-logging` |\n|
`@kbn/logging-mocks` |\n`src/platform/packages/shared/kbn-logging-mocks`
|\n| `@kbn/router-to-openapispec`
|\n`src/platform/packages/shared/kbn-router-to-openapispec` |\n|
`@kbn/server-http-tools`
|\n`src/platform/packages/shared/kbn-server-http-tools` |\n| `@kbn/std`
| `src/platform/packages/shared/kbn-std` |\n| `@kbn/utility-types`
|\n`src/platform/packages/shared/kbn-utility-types` |\n| `@kbn/zod` |
`src/platform/packages/shared/kbn-zod` |\n\n---------\n\nCo-authored-by:
Alejandro Fernández Haro <alejandro.haro@elastic.co>\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"6049493e4a2372ea22986b231ad2bd59584fe9b8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201653","number":201653,"mergeCommit":{"message":"Sustainable
Kibana Architecture: Move modules owned by `@elastic/kibana-core`
(#201653)\n\n## Summary\n\nStart relocating Kibana modules (packages and
plugins) to the new folder\nstructure, according to the _Kibana
Sustainable Architecture_\ninitiative.\n#### 16 plugin(s) are going to
be relocated:\n\n| Id | Target folder |\n| -- | ------------- |\n|
`@kbn/cloud-chat-plugin`
|\n`x-pack/platform/plugins/private/cloud_integrations/cloud_chat` |\n|
`@kbn/cloud-experiments-plugin`
|\n`x-pack/platform/plugins/shared/cloud_integrations/cloud_experiments`
|\n| `@kbn/cloud-full-story-plugin`
|\n`x-pack/platform/plugins/private/cloud_integrations/cloud_full_story`
|\n| `@kbn/cloud-links-plugin`
|\n`x-pack/platform/plugins/private/cloud_integrations/cloud_links` |\n|
`@kbn/cloud-plugin` | `x-pack/platform/plugins/shared/cloud` |\n|
`@kbn/features-plugin` | `x-pack/platform/plugins/shared/features` |\n|
`@kbn/ftr-apis-plugin` | `src/platform/plugins/private/ftr_apis` |\n|
`@kbn/kibana-usage-collection-plugin`
|\n`src/platform/plugins/private/kibana_usage_collection` |\n|
`@kbn/licensing-plugin` | `x-pack/platform/plugins/shared/licensing`
|\n| `@kbn/newsfeed-plugin` | `src/platform/plugins/shared/newsfeed`
|\n| `@kbn/saved-objects-management-plugin`
|\n`src/platform/plugins/shared/saved_objects_management` |\n|
`@kbn/telemetry-collection-manager-plugin`
|\n`src/platform/plugins/shared/telemetry_collection_manager` |\n|
`@kbn/telemetry-collection-xpack-plugin`
|\n`x-pack/platform/plugins/private/telemetry_collection_xpack` |\n|
`@kbn/telemetry-management-section-plugin`
|\n`src/platform/plugins/shared/telemetry_management_section` |\n|
`@kbn/telemetry-plugin` | `src/platform/plugins/shared/telemetry` |\n|
`@kbn/usage-collection-plugin`
|\n`src/platform/plugins/shared/usage_collection` |\n\n#### 22
package(s) are going to be relocated:\n\n| Id | Target folder |\n| -- |
------------- |\n| `@kbn/analytics` |
`src/platform/packages/shared/kbn-analytics` |\n|
`@kbn/analytics-collection-utils`
|\n`src/platform/packages/private/analytics/utils/analytics_collection_utils`\n|\n|
`@kbn/apm-config-loader`
|\n`src/platform/packages/private/kbn-apm-config-loader` |\n|
`@kbn/cloud` | `src/platform/packages/shared/cloud` |\n| `@kbn/config` |
`src/platform/packages/shared/kbn-config` |\n| `@kbn/config-mocks` |
`src/platform/packages/private/kbn-config-mocks`\n|\n|
`@kbn/config-schema` |\n`src/platform/packages/shared/kbn-config-schema`
|\n| `@kbn/crypto-browser`
|\n`src/platform/packages/shared/kbn-crypto-browser` |\n|
`@kbn/ebt-tools` | `src/platform/packages/shared/kbn-ebt-tools` |\n|
`@kbn/es-errors` | `src/platform/packages/shared/kbn-es-errors` |\n|
`@kbn/es-types` | `src/platform/packages/shared/kbn-es-types` |\n|
`@kbn/hapi-mocks` | `src/platform/packages/private/kbn-hapi-mocks` |\n|
`@kbn/health-gateway-server`
|\n`src/platform/packages/private/kbn-health-gateway-server` |\n|
`@kbn/i18n` | `src/platform/packages/shared/kbn-i18n` |\n|
`@kbn/i18n-react` | `src/platform/packages/shared/kbn-i18n-react` |\n|
`@kbn/logging` | `src/platform/packages/shared/kbn-logging` |\n|
`@kbn/logging-mocks` |\n`src/platform/packages/shared/kbn-logging-mocks`
|\n| `@kbn/router-to-openapispec`
|\n`src/platform/packages/shared/kbn-router-to-openapispec` |\n|
`@kbn/server-http-tools`
|\n`src/platform/packages/shared/kbn-server-http-tools` |\n| `@kbn/std`
| `src/platform/packages/shared/kbn-std` |\n| `@kbn/utility-types`
|\n`src/platform/packages/shared/kbn-utility-types` |\n| `@kbn/zod` |
`src/platform/packages/shared/kbn-zod` |\n\n---------\n\nCo-authored-by:
Alejandro Fernández Haro <alejandro.haro@elastic.co>\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"6049493e4a2372ea22986b231ad2bd59584fe9b8"}}]}]
BACKPORT-->

---------

Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co>
 2025-01-05 16:32:00 +01:00
Rodney Norris
046324b342
[8.x] [Search] Deprecate canDeployEntSearch config value (#204272) (#204585) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Search] Deprecate canDeployEntSearch config value
(#204272)](https://github.com/elastic/kibana/pull/204272)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Rodney
Norris","email":"rodney.norris@elastic.co"},"sourceCommit":{"committedDate":"2024-12-17T13:16:33Z","message":"[Search]
Deprecate canDeployEntSearch config value
(#204272)","sha":"9f53fbbcc38cf709f0202e39b5fce7004a88e87b","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:prev-minor","v8.18.0"],"number":204272,"url":"https://github.com/elastic/kibana/pull/204272","mergeCommit":{"message":"[Search]
Deprecate canDeployEntSearch config value
(#204272)","sha":"9f53fbbcc38cf709f0202e39b5fce7004a88e87b"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204272","number":204272,"mergeCommit":{"message":"[Search]
Deprecate canDeployEntSearch config value
(#204272)","sha":"9f53fbbcc38cf709f0202e39b5fce7004a88e87b"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2024-12-17 14:24:47 -06:00
Kibana Machine
e843309023
[8.x] [EuiProvider] Hide unwanted toast until a fix can be done !! (#203244) (#203327) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[EuiProvider] Hide unwanted toast until a fix can be done !!
(#203244)](https://github.com/elastic/kibana/pull/203244)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2024-12-06T18:59:55Z","message":"[EuiProvider]
Hide unwanted toast until a fix can be done !! (#203244)\n\n##
Summary\n\nHiding this until it can be fixed
via\nhttps://github.com/elastic/kibana/issues/201805 !!\n\n<img
width=\"1341\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/64d86aca-9c0e-4e94-9449-5f6a1c6a3288\">","sha":"354858264f84b624a6a4a1fc7a9b2961b7ba6ec0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor"],"title":"[EuiProvider]
Hide unwanted toast until a fix can be done
!!","number":203244,"url":"https://github.com/elastic/kibana/pull/203244","mergeCommit":{"message":"[EuiProvider]
Hide unwanted toast until a fix can be done !! (#203244)\n\n##
Summary\n\nHiding this until it can be fixed
via\nhttps://github.com/elastic/kibana/issues/201805 !!\n\n<img
width=\"1341\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/64d86aca-9c0e-4e94-9449-5f6a1c6a3288\">","sha":"354858264f84b624a6a4a1fc7a9b2961b7ba6ec0"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203244","number":203244,"mergeCommit":{"message":"[EuiProvider]
Hide unwanted toast until a fix can be done !! (#203244)\n\n##
Summary\n\nHiding this until it can be fixed
via\nhttps://github.com/elastic/kibana/issues/201805 !!\n\n<img
width=\"1341\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/64d86aca-9c0e-4e94-9449-5f6a1c6a3288\">","sha":"354858264f84b624a6a4a1fc7a9b2961b7ba6ec0"}}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad31comp@gmail.com>
 2024-12-06 14:45:49 -06:00
Tim Sullivan
d2a78a91b4
[8.x] Preparation for High Contrast Mode, Core/SharedUX domains (#202606) (#203147) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Preparation for High Contrast Mode, Core/SharedUX domains
(#202606)](https://github.com/elastic/kibana/pull/202606)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Tim
Sullivan","email":"tsullivan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-05T15:26:41Z","message":"Preparation
for High Contrast Mode, Core/SharedUX domains (#202606)\n\n##
Summary\r\n\r\n**Reviewers: Please test the code paths affected by this
PR. See the\r\n\"Risks\" section below.**\r\n\r\nPart of work for
enabling \"high contrast mode\" in Kibana.
See\r\nhttps://github.com/elastic/kibana/issues/176219.\r\n\r\n**Background:**\r\nKibana
will soon have a user profile setting to allow users to enable\r\n\"high
contrast mode.\" This setting will activate a flag
with\r\n`<EuiProvider>` that causes EUI components to render with
higher\r\ncontrast visual elements. Consumer plugins and packages need
to be\r\nupdated selected places where `<EuiProvider>` is wrapped, to
pass the\r\n`UserProfileService` service dependency from the CoreStart
contract.\r\n\r\n**NOTE:** **EUI currently does not yet support the
high-contrast mode\r\nflag**, but support for that is expected to come
in around 2 weeks.\r\nThese first PRs are simply preparing the code by
wiring up the\r\n`UserProvideService`.\r\n\r\n### Checklist\r\n\r\nCheck
the PR satisfies following conditions. \r\n\r\nReviewers should verify
this PR satisfies this list as well.\r\n\r\n- [X] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [X] The PR
description includes the appropriate Release Notes section,\r\nand the
correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Risks\r\n\r\nDoes this PR introduce any risks? For example, consider
risks like hard\r\nto test bugs, performance regression, potential of
data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for
each identified\r\nrisk. Invite stakeholders and evaluate how to proceed
before merging.\r\n\r\n- [ ] [medium/high] The implementor of this
change did not manually test\r\nthe affected code paths and relied on
type-checking and functional tests\r\nto drive the changes. Code owners
for this PR need to manually test the\r\naffected code paths.\r\n- [ ]
[medium] The `UserProfileService` dependency comes from the\r\nCoreStart
contract. If acquiring the service causes synchronous code to\r\nbecome
asynchronous, check for race conditions or errors in rendering\r\nReact
components. Code owners for this PR need to manually test
the\r\naffected code paths.\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"6178e8295dc35343ab1847416a6d40432a35e4a5","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","Team:SharedUX","backport:prev-minor"],"number":202606,"url":"https://github.com/elastic/kibana/pull/202606","mergeCommit":{"message":"Preparation
for High Contrast Mode, Core/SharedUX domains (#202606)\n\n##
Summary\r\n\r\n**Reviewers: Please test the code paths affected by this
PR. See the\r\n\"Risks\" section below.**\r\n\r\nPart of work for
enabling \"high contrast mode\" in Kibana.
See\r\nhttps://github.com/elastic/kibana/issues/176219.\r\n\r\n**Background:**\r\nKibana
will soon have a user profile setting to allow users to enable\r\n\"high
contrast mode.\" This setting will activate a flag
with\r\n`<EuiProvider>` that causes EUI components to render with
higher\r\ncontrast visual elements. Consumer plugins and packages need
to be\r\nupdated selected places where `<EuiProvider>` is wrapped, to
pass the\r\n`UserProfileService` service dependency from the CoreStart
contract.\r\n\r\n**NOTE:** **EUI currently does not yet support the
high-contrast mode\r\nflag**, but support for that is expected to come
in around 2 weeks.\r\nThese first PRs are simply preparing the code by
wiring up the\r\n`UserProvideService`.\r\n\r\n### Checklist\r\n\r\nCheck
the PR satisfies following conditions. \r\n\r\nReviewers should verify
this PR satisfies this list as well.\r\n\r\n- [X] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [X] The PR
description includes the appropriate Release Notes section,\r\nand the
correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Risks\r\n\r\nDoes this PR introduce any risks? For example, consider
risks like hard\r\nto test bugs, performance regression, potential of
data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for
each identified\r\nrisk. Invite stakeholders and evaluate how to proceed
before merging.\r\n\r\n- [ ] [medium/high] The implementor of this
change did not manually test\r\nthe affected code paths and relied on
type-checking and functional tests\r\nto drive the changes. Code owners
for this PR need to manually test the\r\naffected code paths.\r\n- [ ]
[medium] The `UserProfileService` dependency comes from the\r\nCoreStart
contract. If acquiring the service causes synchronous code to\r\nbecome
asynchronous, check for race conditions or errors in rendering\r\nReact
components. Code owners for this PR need to manually test
the\r\naffected code paths.\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"6178e8295dc35343ab1847416a6d40432a35e4a5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202606","number":202606,"mergeCommit":{"message":"Preparation
for High Contrast Mode, Core/SharedUX domains (#202606)\n\n##
Summary\r\n\r\n**Reviewers: Please test the code paths affected by this
PR. See the\r\n\"Risks\" section below.**\r\n\r\nPart of work for
enabling \"high contrast mode\" in Kibana.
See\r\nhttps://github.com/elastic/kibana/issues/176219.\r\n\r\n**Background:**\r\nKibana
will soon have a user profile setting to allow users to enable\r\n\"high
contrast mode.\" This setting will activate a flag
with\r\n`<EuiProvider>` that causes EUI components to render with
higher\r\ncontrast visual elements. Consumer plugins and packages need
to be\r\nupdated selected places where `<EuiProvider>` is wrapped, to
pass the\r\n`UserProfileService` service dependency from the CoreStart
contract.\r\n\r\n**NOTE:** **EUI currently does not yet support the
high-contrast mode\r\nflag**, but support for that is expected to come
in around 2 weeks.\r\nThese first PRs are simply preparing the code by
wiring up the\r\n`UserProvideService`.\r\n\r\n### Checklist\r\n\r\nCheck
the PR satisfies following conditions. \r\n\r\nReviewers should verify
this PR satisfies this list as well.\r\n\r\n- [X] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [X] The PR
description includes the appropriate Release Notes section,\r\nand the
correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Risks\r\n\r\nDoes this PR introduce any risks? For example, consider
risks like hard\r\nto test bugs, performance regression, potential of
data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for
each identified\r\nrisk. Invite stakeholders and evaluate how to proceed
before merging.\r\n\r\n- [ ] [medium/high] The implementor of this
change did not manually test\r\nthe affected code paths and relied on
type-checking and functional tests\r\nto drive the changes. Code owners
for this PR need to manually test the\r\naffected code paths.\r\n- [ ]
[medium] The `UserProfileService` dependency comes from the\r\nCoreStart
contract. If acquiring the service causes synchronous code to\r\nbecome
asynchronous, check for race conditions or errors in rendering\r\nReact
components. Code owners for this PR need to manually test
the\r\naffected code paths.\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"6178e8295dc35343ab1847416a6d40432a35e4a5"}}]}]
BACKPORT-->
 2024-12-06 10:02:27 +01:00
Kibana Machine
53e01df17c
[8.x] [UA] Support Deprecated Data Streams Migrations (#202204) (#202593) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[UA] Support Deprecated Data Streams Migrations
(#202204)](https://github.com/elastic/kibana/pull/202204)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Ahmad
Bamieh","email":"ahmad.bamyeh@elastic.co"},"sourceCommit":{"committedDate":"2024-12-02T21:53:24Z","message":"[UA]
Support Deprecated Data Streams Migrations (#202204)\n\n##
Summary\r\n\r\n- [x] Fix UA currently failing to return upgrade
status\r\n- [x] Support surfacing `data_streams` migrations in UA under
the ES tab\r\n- [x] Refactor code for better readablity\r\n- [x] Add
more test cases across the board for all the es migrations\r\nstatus
feature in UA\r\n- [x] Add a `featureSet.migrateDataStreams` to enable
surfacing data\r\nstreams migrations\r\n- [x] Surface data streams in UA
UI\r\n- [x] Take screenshots for a product review discussions\r\n- [x]
Unskip api_integration test cases\r\n\r\n### Imporant Notes\r\n\r\nES
deprecations are hidden behind the `featureSet` flag and will only
be\r\nshown in `8.last` for users.\r\nThis gives us time to review the
copy and implement the corrective\r\naction for reindexing data streams
which is still pending implementaiton\r\nfrom ES side.\r\n\r\nFor now we
will merge this to unblock upgrades in `8.17` and support\r\nsurfacing
data_streams deprecations and add tests.\r\n\r\nFollow up work for
`8.18`\r\n- Add integration Tests\r\n- Update copy of flyout and
documentation link\r\n- Reindexing data streams corrective
action\r\n\r\ncloses
https://github.com/elastic/kibana-team/issues/1293\r\n\r\n##
Screenshots\r\n\r\n#### Overview Page\r\n<img width=\"683\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/246d89ac-02cd-4813-ba38-e2e28df00c8d\">\r\n\r\n####
Elasticsearch deprecation issues Page\r\n\r\n<img width=\"1453\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b5fd5f15-fa44-4acb-b7ff-4973593dcfbb\">\r\n\r\n\r\n####
Data streams deprecation details flyout\r\n<img width=\"778\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/af343f69-7e76-4c91-a6e3-cff29e26df59\">\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"a6b3743e00add07c315eacadda4d0dbb532042ac","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","auto-backport","backport:prev-minor","backport:version","v8.17.0","v8.18.0"],"title":"[UA]
Support Deprecated Data Streams
Migrations","number":202204,"url":"https://github.com/elastic/kibana/pull/202204","mergeCommit":{"message":"[UA]
Support Deprecated Data Streams Migrations (#202204)\n\n##
Summary\r\n\r\n- [x] Fix UA currently failing to return upgrade
status\r\n- [x] Support surfacing `data_streams` migrations in UA under
the ES tab\r\n- [x] Refactor code for better readablity\r\n- [x] Add
more test cases across the board for all the es migrations\r\nstatus
feature in UA\r\n- [x] Add a `featureSet.migrateDataStreams` to enable
surfacing data\r\nstreams migrations\r\n- [x] Surface data streams in UA
UI\r\n- [x] Take screenshots for a product review discussions\r\n- [x]
Unskip api_integration test cases\r\n\r\n### Imporant Notes\r\n\r\nES
deprecations are hidden behind the `featureSet` flag and will only
be\r\nshown in `8.last` for users.\r\nThis gives us time to review the
copy and implement the corrective\r\naction for reindexing data streams
which is still pending implementaiton\r\nfrom ES side.\r\n\r\nFor now we
will merge this to unblock upgrades in `8.17` and support\r\nsurfacing
data_streams deprecations and add tests.\r\n\r\nFollow up work for
`8.18`\r\n- Add integration Tests\r\n- Update copy of flyout and
documentation link\r\n- Reindexing data streams corrective
action\r\n\r\ncloses
https://github.com/elastic/kibana-team/issues/1293\r\n\r\n##
Screenshots\r\n\r\n#### Overview Page\r\n<img width=\"683\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/246d89ac-02cd-4813-ba38-e2e28df00c8d\">\r\n\r\n####
Elasticsearch deprecation issues Page\r\n\r\n<img width=\"1453\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b5fd5f15-fa44-4acb-b7ff-4973593dcfbb\">\r\n\r\n\r\n####
Data streams deprecation details flyout\r\n<img width=\"778\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/af343f69-7e76-4c91-a6e3-cff29e26df59\">\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"a6b3743e00add07c315eacadda4d0dbb532042ac"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202204","number":202204,"mergeCommit":{"message":"[UA]
Support Deprecated Data Streams Migrations (#202204)\n\n##
Summary\r\n\r\n- [x] Fix UA currently failing to return upgrade
status\r\n- [x] Support surfacing `data_streams` migrations in UA under
the ES tab\r\n- [x] Refactor code for better readablity\r\n- [x] Add
more test cases across the board for all the es migrations\r\nstatus
feature in UA\r\n- [x] Add a `featureSet.migrateDataStreams` to enable
surfacing data\r\nstreams migrations\r\n- [x] Surface data streams in UA
UI\r\n- [x] Take screenshots for a product review discussions\r\n- [x]
Unskip api_integration test cases\r\n\r\n### Imporant Notes\r\n\r\nES
deprecations are hidden behind the `featureSet` flag and will only
be\r\nshown in `8.last` for users.\r\nThis gives us time to review the
copy and implement the corrective\r\naction for reindexing data streams
which is still pending implementaiton\r\nfrom ES side.\r\n\r\nFor now we
will merge this to unblock upgrades in `8.17` and support\r\nsurfacing
data_streams deprecations and add tests.\r\n\r\nFollow up work for
`8.18`\r\n- Add integration Tests\r\n- Update copy of flyout and
documentation link\r\n- Reindexing data streams corrective
action\r\n\r\ncloses
https://github.com/elastic/kibana-team/issues/1293\r\n\r\n##
Screenshots\r\n\r\n#### Overview Page\r\n<img width=\"683\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/246d89ac-02cd-4813-ba38-e2e28df00c8d\">\r\n\r\n####
Elasticsearch deprecation issues Page\r\n\r\n<img width=\"1453\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b5fd5f15-fa44-4acb-b7ff-4973593dcfbb\">\r\n\r\n\r\n####
Data streams deprecation details flyout\r\n<img width=\"778\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/af343f69-7e76-4c91-a6e3-cff29e26df59\">\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"a6b3743e00add07c315eacadda4d0dbb532042ac"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Ahmad Bamieh <ahmad.bamyeh@elastic.co>
 2024-12-02 17:46:35 -06:00
Kibana Machine
0ee276594c
[8.x] [deprecations/test plugin]: Check in all spaces (#202356) (#202472) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[deprecations/test plugin]: Check in all spaces
(#202356)](https://github.com/elastic/kibana/pull/202356)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Alejandro Fernández
Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2024-12-02T13:44:40Z","message":"[deprecations/test
plugin]: Check in all spaces
(#202356)","sha":"97dab1030de3e5d1481197bf1d2968b3d6402d7d","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:prev-minor"],"title":"[deprecations/test
plugin]: Check in all
spaces","number":202356,"url":"https://github.com/elastic/kibana/pull/202356","mergeCommit":{"message":"[deprecations/test
plugin]: Check in all spaces
(#202356)","sha":"97dab1030de3e5d1481197bf1d2968b3d6402d7d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202356","number":202356,"mergeCommit":{"message":"[deprecations/test
plugin]: Check in all spaces
(#202356)","sha":"97dab1030de3e5d1481197bf1d2968b3d6402d7d"}}]}]
BACKPORT-->

Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>
 2024-12-02 09:40:12 -06:00
Kibana Machine
dde108c5f5
[8.x] [Stack Monitoring] Switch Logs Explorer locator for Discover locator in Stack Monitoring (#200546) (#202137) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Stack Monitoring] Switch Logs Explorer locator for Discover locator
in Stack Monitoring
(#200546)](https://github.com/elastic/kibana/pull/200546)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Kerry
Gallagher","email":"kerry.gallagher@elastic.co"},"sourceCommit":{"committedDate":"2024-11-28T10:52:38Z","message":"[Stack
Monitoring] Switch Logs Explorer locator for Discover locator in Stack
Monitoring (#200546)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/200256
and\r\nhttps://github.com/elastic/kibana/issues/200218.\r\n\r\n##
Overview of changes\r\n\r\n- The call to
`logsShared.logViews.defineInternalLogView()` is removed\r\nas Log Views
will be deprecated.\r\n- The logs indices that were previously defined
via\r\n`defineInternalLogView()` are now exposed
via\r\n`externalConfig.logsIndices`\r\n- As part of this change
`ui.logs` from `config` is now exposed to\r\nbrowser. Given this is just
an index pattern I don't believe there are\r\nany security concerns
here.\r\n- `getIndexPatterns()` has been moved to common (this makes it
look like\r\nthere's a lot of file changes here).\r\n- The Logs Explorer
locator is swapped for the Discover locator using an\r\nad-hoc data
view.\r\n - This is hidden if Discover isn't available.\r\n\r\nThe
behaviour here should match exactly what we had before, as the
same\r\nindices are constructed from `getIndexPatterns()` and we apply
the same\r\n`query`.\r\n\r\nStack Monitoring reviewer: The path changes
from moving\r\n`getIndexPatterns()` were automated so there shouldn't be
any issues,\r\nbut given it's used extensively please check everything
works as\r\nexpected.\r\n\r\n## Screenshots\r\n\r\n![Screenshot
2024-11-18 at 11
59\r\n45](https://github.com/user-attachments/assets/59b61421-c6f9-4df0-87c5-c67ca732c89f)\r\n\r\n![Screenshot
2024-11-18 at 12
00\r\n15](https://github.com/user-attachments/assets/5a934883-1c35-4551-a045-705b28dfcbb7)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"3e538d67c1378dc438d9f81cb603a7965026ac0c","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-logs","backport:version","v8.18.0","v8.16.2"],"title":"[Stack
Monitoring] Switch Logs Explorer locator for Discover locator in Stack
Monitoring","number":200546,"url":"https://github.com/elastic/kibana/pull/200546","mergeCommit":{"message":"[Stack
Monitoring] Switch Logs Explorer locator for Discover locator in Stack
Monitoring (#200546)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/200256
and\r\nhttps://github.com/elastic/kibana/issues/200218.\r\n\r\n##
Overview of changes\r\n\r\n- The call to
`logsShared.logViews.defineInternalLogView()` is removed\r\nas Log Views
will be deprecated.\r\n- The logs indices that were previously defined
via\r\n`defineInternalLogView()` are now exposed
via\r\n`externalConfig.logsIndices`\r\n- As part of this change
`ui.logs` from `config` is now exposed to\r\nbrowser. Given this is just
an index pattern I don't believe there are\r\nany security concerns
here.\r\n- `getIndexPatterns()` has been moved to common (this makes it
look like\r\nthere's a lot of file changes here).\r\n- The Logs Explorer
locator is swapped for the Discover locator using an\r\nad-hoc data
view.\r\n - This is hidden if Discover isn't available.\r\n\r\nThe
behaviour here should match exactly what we had before, as the
same\r\nindices are constructed from `getIndexPatterns()` and we apply
the same\r\n`query`.\r\n\r\nStack Monitoring reviewer: The path changes
from moving\r\n`getIndexPatterns()` were automated so there shouldn't be
any issues,\r\nbut given it's used extensively please check everything
works as\r\nexpected.\r\n\r\n## Screenshots\r\n\r\n![Screenshot
2024-11-18 at 11
59\r\n45](https://github.com/user-attachments/assets/59b61421-c6f9-4df0-87c5-c67ca732c89f)\r\n\r\n![Screenshot
2024-11-18 at 12
00\r\n15](https://github.com/user-attachments/assets/5a934883-1c35-4551-a045-705b28dfcbb7)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"3e538d67c1378dc438d9f81cb603a7965026ac0c"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200546","number":200546,"mergeCommit":{"message":"[Stack
Monitoring] Switch Logs Explorer locator for Discover locator in Stack
Monitoring (#200546)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/200256
and\r\nhttps://github.com/elastic/kibana/issues/200218.\r\n\r\n##
Overview of changes\r\n\r\n- The call to
`logsShared.logViews.defineInternalLogView()` is removed\r\nas Log Views
will be deprecated.\r\n- The logs indices that were previously defined
via\r\n`defineInternalLogView()` are now exposed
via\r\n`externalConfig.logsIndices`\r\n- As part of this change
`ui.logs` from `config` is now exposed to\r\nbrowser. Given this is just
an index pattern I don't believe there are\r\nany security concerns
here.\r\n- `getIndexPatterns()` has been moved to common (this makes it
look like\r\nthere's a lot of file changes here).\r\n- The Logs Explorer
locator is swapped for the Discover locator using an\r\nad-hoc data
view.\r\n - This is hidden if Discover isn't available.\r\n\r\nThe
behaviour here should match exactly what we had before, as the
same\r\nindices are constructed from `getIndexPatterns()` and we apply
the same\r\n`query`.\r\n\r\nStack Monitoring reviewer: The path changes
from moving\r\n`getIndexPatterns()` were automated so there shouldn't be
any issues,\r\nbut given it's used extensively please check everything
works as\r\nexpected.\r\n\r\n## Screenshots\r\n\r\n![Screenshot
2024-11-18 at 11
59\r\n45](https://github.com/user-attachments/assets/59b61421-c6f9-4df0-87c5-c67ca732c89f)\r\n\r\n![Screenshot
2024-11-18 at 12
00\r\n15](https://github.com/user-attachments/assets/5a934883-1c35-4551-a045-705b28dfcbb7)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"3e538d67c1378dc438d9f81cb603a7965026ac0c"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Kerry Gallagher <kerry.gallagher@elastic.co>
 2024-11-28 06:41:30 -06:00
Sander Philipse
0a5d490226
[8.x] [AI Assistant] Add assistant to Serverless Search (#196832) (#198300) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [AI Assistant] Add assistant to Serverless Search (#196832) (3bc5e2db)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Sander
Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-25T10:03:04Z","message":"[AI
Assistant] Add assistant to Serverless Search (#196832)\n\n##
Summary\r\n\r\nThis adds the AI assistant to Serverless Elasticsearch.
It also disables\r\nthe knowledge base, and disables a few config values
we don't want users\r\nto be able to set in that
context.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Elena Shostak
<165678770+elena-shostak@users.noreply.github.com>","sha":"3bc5e2db73799dc9c7831b6f9da4a52063cf112f"},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[]}]
BACKPORT-->
 2024-10-30 07:48:36 -05:00
Ahmad Bamieh
21dd620443
[8.x][Core] [UA] Support API Deprecations #196081 (#198210) 
## Summary

Backport https://github.com/elastic/kibana/pull/196081
 2024-10-30 07:21:00 +03:00
Kibana Machine
d05d6598d0
[8.x] [Dashboard] Hover actions for panels (#182535) (#197770) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Dashboard] Hover actions for panels
(#182535)](https://github.com/elastic/kibana/pull/182535)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Catherine
Liu","email":"catherine.liu@elastic.co"},"sourceCommit":{"committedDate":"2024-10-25T07:59:41Z","message":"[Dashboard]
Hover actions for panels
(#182535)","sha":"2fdfb8d769442a7591e982a0dcff40fb8eb1699a","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:Dashboard","Feature:Embedding","Team:Presentation","loe:large","impact:medium","Feature:Drilldowns","v9.0.0","Project:Dashboard
Usability","ci:project-deploy-observability","Team:obs-ux-management","backport:version","v8.17.0"],"title":"[Dashboard]
Hover actions for
panels","number":182535,"url":"https://github.com/elastic/kibana/pull/182535","mergeCommit":{"message":"[Dashboard]
Hover actions for panels
(#182535)","sha":"2fdfb8d769442a7591e982a0dcff40fb8eb1699a"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/182535","number":182535,"mergeCommit":{"message":"[Dashboard]
Hover actions for panels
(#182535)","sha":"2fdfb8d769442a7591e982a0dcff40fb8eb1699a"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Catherine Liu <catherine.liu@elastic.co>
 2024-10-25 04:42:51 -05:00
Lukas Olson
f32ce9e65e
[8.x] Fix search session filter functional test (#193812) (#197502) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Fix search session filter functional test
(#193812)](https://github.com/elastic/kibana/pull/193812)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Lukas
Olson","email":"lukas@elastic.co"},"sourceCommit":{"committedDate":"2024-09-27T20:28:53Z","message":"Fix
search session filter functional test (#193812)\n\n##
Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/192510.\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is
usable by keyboard only (learn more\r\nabout [keyboard
accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI
touched in this PR does not create any new axe failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Davis McPhee
<davis.mcphee@elastic.co>","sha":"a9fa11e7daa0b05f6785b7fdc9d28c9b395e73a5","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["failed-test","skipped-test","release_note:skip","backport
missing","v9.0.0","Feature:Search
Sessions","v8.16.0","backport:version"],"number":193812,"url":"https://github.com/elastic/kibana/pull/193812","mergeCommit":{"message":"Fix
search session filter functional test (#193812)\n\n##
Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/192510.\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is
usable by keyboard only (learn more\r\nabout [keyboard
accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI
touched in this PR does not create any new axe failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Davis McPhee
<davis.mcphee@elastic.co>","sha":"a9fa11e7daa0b05f6785b7fdc9d28c9b395e73a5"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/193812","number":193812,"mergeCommit":{"message":"Fix
search session filter functional test (#193812)\n\n##
Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/192510.\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is
usable by keyboard only (learn more\r\nabout [keyboard
accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI
touched in this PR does not create any new axe failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Davis McPhee
<davis.mcphee@elastic.co>","sha":"a9fa11e7daa0b05f6785b7fdc9d28c9b395e73a5"}},{"branch":"8.x","label":"v8.16.0","labelRegex":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2024-10-23 23:27:49 -03:00
Elena Stoeva
47f11ddeb2
[8.x][Index management] Project level retention support (#193715) (#197414) 
# Backport

This will backport the following commits from `main` to `8.x`:
 - https://github.com/elastic/kibana/pull/193715

Note: Created the backport manually because of merge conflicts in
`config/serverless.security.yml`

Co-authored-by: Ignacio Rivas <rivasign@gmail.com>
 2024-10-23 09:14:22 -05:00
Kibana Machine
831f205aa8
[8.x] [Index Management] Added docs count and size for serverless (#191985) (#197387) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Index Management] Added docs count and size for serverless
(#191985)](https://github.com/elastic/kibana/pull/191985)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Yulia
Čech","email":"6585477+yuliacech@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-09-16T11:44:41Z","message":"[Index
Management] Added docs count and size for serverless (#191985)\n\n##
Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/190131\r\n\r\nThis PR adds size
and documents count to indices and data streams tables\r\nin Index
Management on serverless.\r\n\r\n###
Screenrecording\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/51a933e2-e4ef-42a0-9c82-39bf6e194ee0\r\n\r\n\r\n\r\n###
Screenshots \r\n<img width=\"1047\" alt=\"Screenshot 2024-09-06 at 19 20
59\"\r\nsrc=\"https://github.com/user-attachments/assets/8c6d0378-116f-44e3-aaca-0c95f135b1bf\">\r\n<img
width=\"1045\" alt=\"Screenshot 2024-09-06 at 19 21
06\"\r\nsrc=\"https://github.com/user-attachments/assets/37477f7b-e229-4400-9a28-8382f7d1155e\">\r\n<img
width=\"1036\" alt=\"Screenshot 2024-09-06 at 19 27
59\"\r\nsrc=\"https://github.com/user-attachments/assets/0fd2ef1b-3b0c-4d3e-8b56-984281436898\">\r\n<img
width=\"506\" alt=\"Screenshot 2024-09-06 at 19 28
12\"\r\nsrc=\"https://github.com/user-attachments/assets/1823a964-6f6f-464b-9910-e586ccd2e9bb\">\r\n\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is
usable by keyboard only (learn more\r\nabout [keyboard
accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI
touched in this PR does not create any new axe failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3de252e688515e9f84e199b73e5e4246f76b8c19","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Index
Management","Team:Kibana
Management","release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-security","v8.17.0"],"title":"[Index
Management] Added docs count and size for
serverless","number":191985,"url":"https://github.com/elastic/kibana/pull/191985","mergeCommit":{"message":"[Index
Management] Added docs count and size for serverless (#191985)\n\n##
Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/190131\r\n\r\nThis PR adds size
and documents count to indices and data streams tables\r\nin Index
Management on serverless.\r\n\r\n###
Screenrecording\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/51a933e2-e4ef-42a0-9c82-39bf6e194ee0\r\n\r\n\r\n\r\n###
Screenshots \r\n<img width=\"1047\" alt=\"Screenshot 2024-09-06 at 19 20
59\"\r\nsrc=\"https://github.com/user-attachments/assets/8c6d0378-116f-44e3-aaca-0c95f135b1bf\">\r\n<img
width=\"1045\" alt=\"Screenshot 2024-09-06 at 19 21
06\"\r\nsrc=\"https://github.com/user-attachments/assets/37477f7b-e229-4400-9a28-8382f7d1155e\">\r\n<img
width=\"1036\" alt=\"Screenshot 2024-09-06 at 19 27
59\"\r\nsrc=\"https://github.com/user-attachments/assets/0fd2ef1b-3b0c-4d3e-8b56-984281436898\">\r\n<img
width=\"506\" alt=\"Screenshot 2024-09-06 at 19 28
12\"\r\nsrc=\"https://github.com/user-attachments/assets/1823a964-6f6f-464b-9910-e586ccd2e9bb\">\r\n\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is
usable by keyboard only (learn more\r\nabout [keyboard
accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI
touched in this PR does not create any new axe failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3de252e688515e9f84e199b73e5e4246f76b8c19"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/191985","number":191985,"mergeCommit":{"message":"[Index
Management] Added docs count and size for serverless (#191985)\n\n##
Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/190131\r\n\r\nThis PR adds size
and documents count to indices and data streams tables\r\nin Index
Management on serverless.\r\n\r\n###
Screenrecording\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/51a933e2-e4ef-42a0-9c82-39bf6e194ee0\r\n\r\n\r\n\r\n###
Screenshots \r\n<img width=\"1047\" alt=\"Screenshot 2024-09-06 at 19 20
59\"\r\nsrc=\"https://github.com/user-attachments/assets/8c6d0378-116f-44e3-aaca-0c95f135b1bf\">\r\n<img
width=\"1045\" alt=\"Screenshot 2024-09-06 at 19 21
06\"\r\nsrc=\"https://github.com/user-attachments/assets/37477f7b-e229-4400-9a28-8382f7d1155e\">\r\n<img
width=\"1036\" alt=\"Screenshot 2024-09-06 at 19 27
59\"\r\nsrc=\"https://github.com/user-attachments/assets/0fd2ef1b-3b0c-4d3e-8b56-984281436898\">\r\n<img
width=\"506\" alt=\"Screenshot 2024-09-06 at 19 28
12\"\r\nsrc=\"https://github.com/user-attachments/assets/1823a964-6f6f-464b-9910-e586ccd2e9bb\">\r\n\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is
usable by keyboard only (learn more\r\nabout [keyboard
accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI
touched in this PR does not create any new axe failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3de252e688515e9f84e199b73e5e4246f76b8c19"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Yulia Čech <6585477+yuliacech@users.noreply.github.com>
 2024-10-23 06:10:12 -05:00
Kibana Machine
f0ec68a365
[8.x] Add support for GeoIP processor databases in Ingest Pipelines (#190830) (#196420) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Add support for GeoIP processor databases in Ingest Pipelines
(#190830)](https://github.com/elastic/kibana/pull/190830)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Yulia
Čech","email":"6585477+yuliacech@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-15T17:58:43Z","message":"Add
support for GeoIP processor databases in Ingest Pipelines
(#190830)\n\nFixes
https://github.com/elastic/kibana/issues/190818\r\n\r\n##
Summary\r\n\r\nElasticsearch has added support for GeoIP, enabling the
use of paid\r\nGeoIP databases from MaxMind/IPInfo for more accurate and
granular\r\ngeolocation data. As such we should add support to ingest
pipelines UI\r\nfor making this available to the user.\r\n\r\n\r\n* If
the user doesn't have enough privileges, the \"Manage
Pipelines\"\r\nlink and UI won't show.\r\n* Users can add two types of
databases through the UI: MaxMind and\r\nIPinfo. Database names are
predefined by ES, and the user cannot enter\r\ntheir own.\r\n* Certain
types of databases (local and web) can be configured through\r\nES, and
these will appear in the UI, but they cannot be deleted as they\r\nare
read-only.\r\n* When configuring a `IP location` processor, the database
field will\r\ndisplay a list of available and configured databases that
the user can\r\nselect. It also allows for free-text input if the user
wants to\r\nconfigure a database that does not yet exist.\r\n* The new
IP location processor is essentially a clone of the GeoIP\r\nprocessor,
which we are moving away from due to copyright issues.\r\nHowever, it
was decided that GeoIP will remain as is for backward\r\ncompatibility,
and all new work will only be added to IP location
going\r\nforward.\r\n* I left a few mocks in the
`server/routes/api/geoip_database/list.ts `\r\nto try `local/web`
types\r\n\r\n## Release note\r\nThe Ingest Pipelines app now supports
adding and managing databases for\r\nthe GeoIP processor. Additionally,
the pipeline creation flow now\r\nincludes support for the IP Location
processor.\r\n\r\n<details>\r\n<summary>Screenshots</summary>\r\n\r\n![Screenshot
2024-10-07 at 09
36\r\n31](https://github.com/user-attachments/assets/60d438cc-6658-4475-bd27-036c7d13d496)\r\n![Screenshot
2024-10-07 at 09
38\r\n58](https://github.com/user-attachments/assets/7c08e94f-b35c-4e78-a204-1fb456d88181)\r\n![Screenshot
2024-10-07 at 09
47\r\n08](https://github.com/user-attachments/assets/2baca0bd-811d-4dd5-9eb6-9b3f41579249)\r\n![Screenshot
2024-10-07 at 09
47\r\n20](https://github.com/user-attachments/assets/74d8664c-8c73-41f3-8cd5-e0670f3ada77)\r\n![Screenshot
2024-10-07 at 09
48\r\n19](https://github.com/user-attachments/assets/9fb4c186-6224-404c-a8d6-5c44c14da951)\r\n![Screenshot
2024-10-07 at 09
48\r\n25](https://github.com/user-attachments/assets/07e4909d-2613-45aa-918b-11a189e14f6f)\r\n\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Ignacio
Rivas <rivasign@gmail.com>\r\nCo-authored-by: Elena Stoeva
<elenastoeva99@gmail.com>\r\nCo-authored-by: Elena Stoeva
<59341489+ElenaStoeva@users.noreply.github.com>\r\nCo-authored-by:
Matthew Kime
<matt@mattki.me>","sha":"302ac0d336feb861522c9ca3f3c271e172b86ae9","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Kibana
Management","v9.0.0","Feature:Ingest Node
Pipelines","release_note:feature","backport:prev-minor","ci:cloud-deploy"],"title":"Add
support for GeoIP processor databases in Ingest
Pipelines","number":190830,"url":"https://github.com/elastic/kibana/pull/190830","mergeCommit":{"message":"Add
support for GeoIP processor databases in Ingest Pipelines
(#190830)\n\nFixes
https://github.com/elastic/kibana/issues/190818\r\n\r\n##
Summary\r\n\r\nElasticsearch has added support for GeoIP, enabling the
use of paid\r\nGeoIP databases from MaxMind/IPInfo for more accurate and
granular\r\ngeolocation data. As such we should add support to ingest
pipelines UI\r\nfor making this available to the user.\r\n\r\n\r\n* If
the user doesn't have enough privileges, the \"Manage
Pipelines\"\r\nlink and UI won't show.\r\n* Users can add two types of
databases through the UI: MaxMind and\r\nIPinfo. Database names are
predefined by ES, and the user cannot enter\r\ntheir own.\r\n* Certain
types of databases (local and web) can be configured through\r\nES, and
these will appear in the UI, but they cannot be deleted as they\r\nare
read-only.\r\n* When configuring a `IP location` processor, the database
field will\r\ndisplay a list of available and configured databases that
the user can\r\nselect. It also allows for free-text input if the user
wants to\r\nconfigure a database that does not yet exist.\r\n* The new
IP location processor is essentially a clone of the GeoIP\r\nprocessor,
which we are moving away from due to copyright issues.\r\nHowever, it
was decided that GeoIP will remain as is for backward\r\ncompatibility,
and all new work will only be added to IP location
going\r\nforward.\r\n* I left a few mocks in the
`server/routes/api/geoip_database/list.ts `\r\nto try `local/web`
types\r\n\r\n## Release note\r\nThe Ingest Pipelines app now supports
adding and managing databases for\r\nthe GeoIP processor. Additionally,
the pipeline creation flow now\r\nincludes support for the IP Location
processor.\r\n\r\n<details>\r\n<summary>Screenshots</summary>\r\n\r\n![Screenshot
2024-10-07 at 09
36\r\n31](https://github.com/user-attachments/assets/60d438cc-6658-4475-bd27-036c7d13d496)\r\n![Screenshot
2024-10-07 at 09
38\r\n58](https://github.com/user-attachments/assets/7c08e94f-b35c-4e78-a204-1fb456d88181)\r\n![Screenshot
2024-10-07 at 09
47\r\n08](https://github.com/user-attachments/assets/2baca0bd-811d-4dd5-9eb6-9b3f41579249)\r\n![Screenshot
2024-10-07 at 09
47\r\n20](https://github.com/user-attachments/assets/74d8664c-8c73-41f3-8cd5-e0670f3ada77)\r\n![Screenshot
2024-10-07 at 09
48\r\n19](https://github.com/user-attachments/assets/9fb4c186-6224-404c-a8d6-5c44c14da951)\r\n![Screenshot
2024-10-07 at 09
48\r\n25](https://github.com/user-attachments/assets/07e4909d-2613-45aa-918b-11a189e14f6f)\r\n\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Ignacio
Rivas <rivasign@gmail.com>\r\nCo-authored-by: Elena Stoeva
<elenastoeva99@gmail.com>\r\nCo-authored-by: Elena Stoeva
<59341489+ElenaStoeva@users.noreply.github.com>\r\nCo-authored-by:
Matthew Kime
<matt@mattki.me>","sha":"302ac0d336feb861522c9ca3f3c271e172b86ae9"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/190830","number":190830,"mergeCommit":{"message":"Add
support for GeoIP processor databases in Ingest Pipelines
(#190830)\n\nFixes
https://github.com/elastic/kibana/issues/190818\r\n\r\n##
Summary\r\n\r\nElasticsearch has added support for GeoIP, enabling the
use of paid\r\nGeoIP databases from MaxMind/IPInfo for more accurate and
granular\r\ngeolocation data. As such we should add support to ingest
pipelines UI\r\nfor making this available to the user.\r\n\r\n\r\n* If
the user doesn't have enough privileges, the \"Manage
Pipelines\"\r\nlink and UI won't show.\r\n* Users can add two types of
databases through the UI: MaxMind and\r\nIPinfo. Database names are
predefined by ES, and the user cannot enter\r\ntheir own.\r\n* Certain
types of databases (local and web) can be configured through\r\nES, and
these will appear in the UI, but they cannot be deleted as they\r\nare
read-only.\r\n* When configuring a `IP location` processor, the database
field will\r\ndisplay a list of available and configured databases that
the user can\r\nselect. It also allows for free-text input if the user
wants to\r\nconfigure a database that does not yet exist.\r\n* The new
IP location processor is essentially a clone of the GeoIP\r\nprocessor,
which we are moving away from due to copyright issues.\r\nHowever, it
was decided that GeoIP will remain as is for backward\r\ncompatibility,
and all new work will only be added to IP location
going\r\nforward.\r\n* I left a few mocks in the
`server/routes/api/geoip_database/list.ts `\r\nto try `local/web`
types\r\n\r\n## Release note\r\nThe Ingest Pipelines app now supports
adding and managing databases for\r\nthe GeoIP processor. Additionally,
the pipeline creation flow now\r\nincludes support for the IP Location
processor.\r\n\r\n<details>\r\n<summary>Screenshots</summary>\r\n\r\n![Screenshot
2024-10-07 at 09
36\r\n31](https://github.com/user-attachments/assets/60d438cc-6658-4475-bd27-036c7d13d496)\r\n![Screenshot
2024-10-07 at 09
38\r\n58](https://github.com/user-attachments/assets/7c08e94f-b35c-4e78-a204-1fb456d88181)\r\n![Screenshot
2024-10-07 at 09
47\r\n08](https://github.com/user-attachments/assets/2baca0bd-811d-4dd5-9eb6-9b3f41579249)\r\n![Screenshot
2024-10-07 at 09
47\r\n20](https://github.com/user-attachments/assets/74d8664c-8c73-41f3-8cd5-e0670f3ada77)\r\n![Screenshot
2024-10-07 at 09
48\r\n19](https://github.com/user-attachments/assets/9fb4c186-6224-404c-a8d6-5c44c14da951)\r\n![Screenshot
2024-10-07 at 09
48\r\n25](https://github.com/user-attachments/assets/07e4909d-2613-45aa-918b-11a189e14f6f)\r\n\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Ignacio
Rivas <rivasign@gmail.com>\r\nCo-authored-by: Elena Stoeva
<elenastoeva99@gmail.com>\r\nCo-authored-by: Elena Stoeva
<59341489+ElenaStoeva@users.noreply.github.com>\r\nCo-authored-by:
Matthew Kime
<matt@mattki.me>","sha":"302ac0d336feb861522c9ca3f3c271e172b86ae9"}}]}]
BACKPORT-->

Co-authored-by: Elena Stoeva <elenastoeva99@gmail.com>
 2024-10-15 17:06:15 -05:00
Kibana Machine
107ff84cbf
[8.x] [ML] Update vCPUs ranges for start model deployment (#195617) (#196156) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ML] Update vCPUs ranges for start model deployment
(#195617)](https://github.com/elastic/kibana/pull/195617)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Dima
Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2024-10-14T14:38:26Z","message":"[ML]
Update vCPUs ranges for start model deployment (#195617)\n\n##
Summary\r\n\r\n#### Different vCPUs ranges and enabling support for
static allocations\r\nbased on the serverless project type\r\n\r\n- Each
serverless config yml,
e.g.\r\n[search.es.yml](84b3b79a15/config/serverless.es.yml (L61))\r\nnow
contains parameters required for start model
deployment:\r\n\r\n```yml\r\nxpack.ml.nlp:\r\n enabled: true\r\n
modelDeployment:\r\n allowStaticAllocations: true\r\n vCPURange:\r\n
low:\r\n min: 0\r\n max: 2\r\n static: 2\r\n medium:\r\n min: 1\r\n max:
32\r\n static: 32\r\n high:\r\n min: 1\r\n max: 512\r\n static:
512\r\n```\r\n\r\nNote: _There will be no static allocations option for
serverless O11y\r\nand serverless Security._\r\n\r\n#### The minimum
values of vCPUs\r\n\r\n- 0 for the Low usage level on both serverless
and ESS.\r\n- 1 for the Medium and High usage levels on both serverless
and ESS.\r\n \r\n#### The default vCPUs usage levels\r\n- Low in
serverless.\r\n- Medium in ESS and on-prem\r\n\r\n### Checklist\r\n\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"13897083dc8c465a16ddb3856d4e4904b9629610","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","v9.0.0","Feature:3rd
Party
Models","Team:ML","ci:project-deploy-elasticsearch","ci:project-deploy-observability","v8.16.0","backport:version"],"title":"[ML]
Update vCPUs ranges for start model deployment
","number":195617,"url":"https://github.com/elastic/kibana/pull/195617","mergeCommit":{"message":"[ML]
Update vCPUs ranges for start model deployment (#195617)\n\n##
Summary\r\n\r\n#### Different vCPUs ranges and enabling support for
static allocations\r\nbased on the serverless project type\r\n\r\n- Each
serverless config yml,
e.g.\r\n[search.es.yml](84b3b79a15/config/serverless.es.yml (L61))\r\nnow
contains parameters required for start model
deployment:\r\n\r\n```yml\r\nxpack.ml.nlp:\r\n enabled: true\r\n
modelDeployment:\r\n allowStaticAllocations: true\r\n vCPURange:\r\n
low:\r\n min: 0\r\n max: 2\r\n static: 2\r\n medium:\r\n min: 1\r\n max:
32\r\n static: 32\r\n high:\r\n min: 1\r\n max: 512\r\n static:
512\r\n```\r\n\r\nNote: _There will be no static allocations option for
serverless O11y\r\nand serverless Security._\r\n\r\n#### The minimum
values of vCPUs\r\n\r\n- 0 for the Low usage level on both serverless
and ESS.\r\n- 1 for the Medium and High usage levels on both serverless
and ESS.\r\n \r\n#### The default vCPUs usage levels\r\n- Low in
serverless.\r\n- Medium in ESS and on-prem\r\n\r\n### Checklist\r\n\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"13897083dc8c465a16ddb3856d4e4904b9629610"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/195617","number":195617,"mergeCommit":{"message":"[ML]
Update vCPUs ranges for start model deployment (#195617)\n\n##
Summary\r\n\r\n#### Different vCPUs ranges and enabling support for
static allocations\r\nbased on the serverless project type\r\n\r\n- Each
serverless config yml,
e.g.\r\n[search.es.yml](84b3b79a15/config/serverless.es.yml (L61))\r\nnow
contains parameters required for start model
deployment:\r\n\r\n```yml\r\nxpack.ml.nlp:\r\n enabled: true\r\n
modelDeployment:\r\n allowStaticAllocations: true\r\n vCPURange:\r\n
low:\r\n min: 0\r\n max: 2\r\n static: 2\r\n medium:\r\n min: 1\r\n max:
32\r\n static: 32\r\n high:\r\n min: 1\r\n max: 512\r\n static:
512\r\n```\r\n\r\nNote: _There will be no static allocations option for
serverless O11y\r\nand serverless Security._\r\n\r\n#### The minimum
values of vCPUs\r\n\r\n- 0 for the Low usage level on both serverless
and ESS.\r\n- 1 for the Medium and High usage levels on both serverless
and ESS.\r\n \r\n#### The default vCPUs usage levels\r\n- Low in
serverless.\r\n- Medium in ESS and on-prem\r\n\r\n### Checklist\r\n\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"13897083dc8c465a16ddb3856d4e4904b9629610"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co>
 2024-10-14 11:27:52 -05:00
Kibana Machine
4951ab959c
[8.x] [Search Assistant] Use scopes to modify behavior contextually (#195785) (#196014) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Search Assistant] Use scopes to modify behavior contextually
(#195785)](https://github.com/elastic/kibana/pull/195785)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Sander
Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-11T23:09:06Z","message":"[Search
Assistant] Use scopes to modify behavior contextually (#195785)\n\n##
Summary\r\n\r\nThis actually uses the Search Assistant scope to modify
the assistant's\r\nbehavior depending on the context they're in. The
assistant now:\r\n- Defaults to Observability mode\r\n- Is a Search
assistant in the Search pages\r\n- Switches dynamically, changing
available functions, prompts and\r\ninstructions based on
context\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ee341d5f801ca42ed26acf0544b0bc59948d0214","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","Team:Obs
AI
Assistant","ci:project-deploy-observability","v8.16.0","backport:version"],"title":"[Search
Assistant] Use scopes to modify behavior
contextually","number":195785,"url":"https://github.com/elastic/kibana/pull/195785","mergeCommit":{"message":"[Search
Assistant] Use scopes to modify behavior contextually (#195785)\n\n##
Summary\r\n\r\nThis actually uses the Search Assistant scope to modify
the assistant's\r\nbehavior depending on the context they're in. The
assistant now:\r\n- Defaults to Observability mode\r\n- Is a Search
assistant in the Search pages\r\n- Switches dynamically, changing
available functions, prompts and\r\ninstructions based on
context\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ee341d5f801ca42ed26acf0544b0bc59948d0214"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/195785","number":195785,"mergeCommit":{"message":"[Search
Assistant] Use scopes to modify behavior contextually (#195785)\n\n##
Summary\r\n\r\nThis actually uses the Search Assistant scope to modify
the assistant's\r\nbehavior depending on the context they're in. The
assistant now:\r\n- Defaults to Observability mode\r\n- Is a Search
assistant in the Search pages\r\n- Switches dynamically, changing
available functions, prompts and\r\ninstructions based on
context\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ee341d5f801ca42ed26acf0544b0bc59948d0214"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/196013","number":196013,"state":"OPEN"}]}]
BACKPORT-->

Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com>
 2024-10-12 10:42:43 -05:00
Sander Philipse
8fef06fa55
[8.x] Extract AI assistant to package (#194552) (#196011) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Extract AI assistant to package
(#194552)](https://github.com/elastic/kibana/pull/194552)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Sander
Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-10T13:11:49Z","message":"Extract
AI assistant to package (#194552)\n\n## Summary\r\n\r\nThis extracts the
Observability AI Assistant into a shared package so\r\nSearch and
Observability can both consume it.\r\n\r\nA few notes:\r\n\r\nThis still
relies on significantly tight coupling with the Obs AI\r\nassistant
plugin, which we will want to slowly decouple over time. It\r\nmeans
that currently to consume this in multiple places, you need
to\r\nprovide a number of plugins for useKibana. Hopefully we can get
rid of\r\nthat and replace them with props eventually and make the
interface a\r\nlittle less
plugin-dependent.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8a3a05927bdbe264c491b4034ff5d81674f3db73","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","Team:Obs
AI
Assistant","ci:project-deploy-observability","v8.16.0","backport:version"],"number":194552,"url":"https://github.com/elastic/kibana/pull/194552","mergeCommit":{"message":"Extract
AI assistant to package (#194552)\n\n## Summary\r\n\r\nThis extracts the
Observability AI Assistant into a shared package so\r\nSearch and
Observability can both consume it.\r\n\r\nA few notes:\r\n\r\nThis still
relies on significantly tight coupling with the Obs AI\r\nassistant
plugin, which we will want to slowly decouple over time. It\r\nmeans
that currently to consume this in multiple places, you need
to\r\nprovide a number of plugins for useKibana. Hopefully we can get
rid of\r\nthat and replace them with props eventually and make the
interface a\r\nlittle less
plugin-dependent.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8a3a05927bdbe264c491b4034ff5d81674f3db73"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/194552","number":194552,"mergeCommit":{"message":"Extract
AI assistant to package (#194552)\n\n## Summary\r\n\r\nThis extracts the
Observability AI Assistant into a shared package so\r\nSearch and
Observability can both consume it.\r\n\r\nA few notes:\r\n\r\nThis still
relies on significantly tight coupling with the Obs AI\r\nassistant
plugin, which we will want to slowly decouple over time. It\r\nmeans
that currently to consume this in multiple places, you need
to\r\nprovide a number of plugins for useKibana. Hopefully we can get
rid of\r\nthat and replace them with props eventually and make the
interface a\r\nlittle less
plugin-dependent.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8a3a05927bdbe264c491b4034ff5d81674f3db73"}},{"branch":"8.x","label":"v8.16.0","labelRegex":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2024-10-12 13:19:36 +02:00
Kibana Machine
00462139aa
[8.x] [Search][Homepage] Remove usage (#194870) (#195137) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Search][Homepage] Remove usage
(#194870)](https://github.com/elastic/kibana/pull/194870)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Rodney
Norris","email":"rodney.norris@elastic.co"},"sourceCommit":{"committedDate":"2024-10-04T18:30:37Z","message":"[Search][Homepage]
Remove usage (#194870)\n\n## Summary\r\n\r\nRemoving search home usage
from serverless search and enterprise search.\r\nThe search home page
project is on hold while we re-assess requirements.\r\nUntil we know
when we are starting that back up I'm removing the feature\r\nflagged
usage to simplify other work. When we spin this back up usage\r\nwill
likely be different anyway with other projects like onboarding
and\r\nthe updating navigation refactor in
enterprise_search.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic
Machine
<elasticmachine@users.noreply.github.com>","sha":"a84b3f841cd952bc3fc511000bf4fbfae4d5b083","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:prev-minor"],"title":"[Search][Homepage]
Remove usage
","number":194870,"url":"https://github.com/elastic/kibana/pull/194870","mergeCommit":{"message":"[Search][Homepage]
Remove usage (#194870)\n\n## Summary\r\n\r\nRemoving search home usage
from serverless search and enterprise search.\r\nThe search home page
project is on hold while we re-assess requirements.\r\nUntil we know
when we are starting that back up I'm removing the feature\r\nflagged
usage to simplify other work. When we spin this back up usage\r\nwill
likely be different anyway with other projects like onboarding
and\r\nthe updating navigation refactor in
enterprise_search.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic
Machine
<elasticmachine@users.noreply.github.com>","sha":"a84b3f841cd952bc3fc511000bf4fbfae4d5b083"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/194870","number":194870,"mergeCommit":{"message":"[Search][Homepage]
Remove usage (#194870)\n\n## Summary\r\n\r\nRemoving search home usage
from serverless search and enterprise search.\r\nThe search home page
project is on hold while we re-assess requirements.\r\nUntil we know
when we are starting that back up I'm removing the feature\r\nflagged
usage to simplify other work. When we spin this back up usage\r\nwill
likely be different anyway with other projects like onboarding
and\r\nthe updating navigation refactor in
enterprise_search.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic
Machine
<elasticmachine@users.noreply.github.com>","sha":"a84b3f841cd952bc3fc511000bf4fbfae4d5b083"}}]}]
BACKPORT-->

Co-authored-by: Rodney Norris <rodney.norris@elastic.co>
 2024-10-04 15:16:52 -05:00
Kibana Machine
5ad385c8ab
[8.x] [Automatic Import] Add experimental features to integration_assistant plugin (#194699) (#194833) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Automatic Import] Add experimental features to integration_assistant
plugin (#194699)](https://github.com/elastic/kibana/pull/194699)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Kylie
Meli","email":"kylie.geller@elastic.co"},"sourceCommit":{"committedDate":"2024-10-03T13:09:52Z","message":"[Automatic
Import] Add experimental features to integration_assistant plugin
(#194699)\n\n## Summary\r\n\r\nThis PR adds experimental features to the
integration_assistant plugin.\r\nI used the fleet and security solutions
plugins as references, and\r\nimplemented them exactly as they have.
Currently nothing is actually\r\nusing this.\r\n\r\nTo be able to
utilize this, add\r\n`xpack.integration_assistant.enableExperimental:
['testFeature']` to the\r\nconfig.\r\n\r\nTested by adding to the config
and verifying correct output in console\r\nvia
[test\r\nlogs](74ddf3786e (diff-177cfac6e94662a2089f6c56000726e1a1924f9222caaf8bcb1312a7583c110eR60)).","sha":"c0e2d95050962021979531a82de20fc3877d4db0","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport"],"title":"[Automatic
Import] Add experimental features to integration_assistant
plugin","number":194699,"url":"https://github.com/elastic/kibana/pull/194699","mergeCommit":{"message":"[Automatic
Import] Add experimental features to integration_assistant plugin
(#194699)\n\n## Summary\r\n\r\nThis PR adds experimental features to the
integration_assistant plugin.\r\nI used the fleet and security solutions
plugins as references, and\r\nimplemented them exactly as they have.
Currently nothing is actually\r\nusing this.\r\n\r\nTo be able to
utilize this, add\r\n`xpack.integration_assistant.enableExperimental:
['testFeature']` to the\r\nconfig.\r\n\r\nTested by adding to the config
and verifying correct output in console\r\nvia
[test\r\nlogs](74ddf3786e (diff-177cfac6e94662a2089f6c56000726e1a1924f9222caaf8bcb1312a7583c110eR60)).","sha":"c0e2d95050962021979531a82de20fc3877d4db0"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/194699","number":194699,"mergeCommit":{"message":"[Automatic
Import] Add experimental features to integration_assistant plugin
(#194699)\n\n## Summary\r\n\r\nThis PR adds experimental features to the
integration_assistant plugin.\r\nI used the fleet and security solutions
plugins as references, and\r\nimplemented them exactly as they have.
Currently nothing is actually\r\nusing this.\r\n\r\nTo be able to
utilize this, add\r\n`xpack.integration_assistant.enableExperimental:
['testFeature']` to the\r\nconfig.\r\n\r\nTested by adding to the config
and verifying correct output in console\r\nvia
[test\r\nlogs](74ddf3786e (diff-177cfac6e94662a2089f6c56000726e1a1924f9222caaf8bcb1312a7583c110eR60)).","sha":"c0e2d95050962021979531a82de20fc3877d4db0"}}]}]
BACKPORT-->

Co-authored-by: Kylie Meli <kylie.geller@elastic.co>
 2024-10-03 09:52:09 -05:00
Kibana Machine
023e3ed826
[8.x] Clean up &#x60;cloud_chat&#x60; (#194571) (#194818) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Clean up &#x60;cloud_chat&#x60;
(#194571)](https://github.com/elastic/kibana/pull/194571)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Anton
Dosov","email":"anton.dosov@elastic.co"},"sourceCommit":{"committedDate":"2024-10-03T11:37:47Z","message":"Clean
up `cloud_chat` (#194571)\n\n## Summary\r\n\r\nClose
https://github.com/elastic/kibana-team/issues/1017\r\n\r\nThis PR
removes the unused Cloud Chat functionality from Kibana. The\r\nchat was
not used for some time. Moreover, we've seen some issues with\r\nit
where users saw it when it wasn't expected. Given the absence
of\r\nautomated tests and the fact that the feature is no longer needed,
we\r\nare removing it to improve the overall maintainability and
reliability\r\nof the codebase. This will also decrease the amount of
code loaded for\r\ntrial users of Kibana in cloud making the app
slightly
faster.","sha":"568e40accaaee06a6dadfec2028263889cf7104a","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor"],"title":"Clean
up
`cloud_chat`","number":194571,"url":"https://github.com/elastic/kibana/pull/194571","mergeCommit":{"message":"Clean
up `cloud_chat` (#194571)\n\n## Summary\r\n\r\nClose
https://github.com/elastic/kibana-team/issues/1017\r\n\r\nThis PR
removes the unused Cloud Chat functionality from Kibana. The\r\nchat was
not used for some time. Moreover, we've seen some issues with\r\nit
where users saw it when it wasn't expected. Given the absence
of\r\nautomated tests and the fact that the feature is no longer needed,
we\r\nare removing it to improve the overall maintainability and
reliability\r\nof the codebase. This will also decrease the amount of
code loaded for\r\ntrial users of Kibana in cloud making the app
slightly
faster.","sha":"568e40accaaee06a6dadfec2028263889cf7104a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/194571","number":194571,"mergeCommit":{"message":"Clean
up `cloud_chat` (#194571)\n\n## Summary\r\n\r\nClose
https://github.com/elastic/kibana-team/issues/1017\r\n\r\nThis PR
removes the unused Cloud Chat functionality from Kibana. The\r\nchat was
not used for some time. Moreover, we've seen some issues with\r\nit
where users saw it when it wasn't expected. Given the absence
of\r\nautomated tests and the fact that the feature is no longer needed,
we\r\nare removing it to improve the overall maintainability and
reliability\r\nof the codebase. This will also decrease the amount of
code loaded for\r\ntrial users of Kibana in cloud making the app
slightly faster.","sha":"568e40accaaee06a6dadfec2028263889cf7104a"}}]}]
BACKPORT-->

Co-authored-by: Anton Dosov <anton.dosov@elastic.co>
 2024-10-03 09:12:16 -05:00
Alejandro Fernández Haro
71ad243504
[8.x] [Feature Flags Service] Hello world 👋 (#188562) (#193519) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Feature Flags Service] Hello world 👋
(#188562)](https://github.com/elastic/kibana/pull/188562)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Alejandro Fernández
Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2024-09-18T16:02:55Z","message":"[Feature
Flags Service] Hello world 👋 (#188562)\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Jean-Louis Leysens
<jloleysens@gmail.com>","sha":"02ce1b91014eb59f019854b01325bbdf983d2218","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Team:Operations","Team:Security","release_note:skip","Team:Observability","Team:Fleet","v9.0.0","Team:
SecuritySolution","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-logs"],"number":188562,"url":"https://github.com/elastic/kibana/pull/188562","mergeCommit":{"message":"[Feature
Flags Service] Hello world 👋 (#188562)\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Jean-Louis Leysens
<jloleysens@gmail.com>","sha":"02ce1b91014eb59f019854b01325bbdf983d2218"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/188562","number":188562,"mergeCommit":{"message":"[Feature
Flags Service] Hello world 👋 (#188562)\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Jean-Louis Leysens
<jloleysens@gmail.com>","sha":"02ce1b91014eb59f019854b01325bbdf983d2218"}}]}]
BACKPORT-->
 2024-09-20 12:21:41 +02:00
Kibana Machine
0ff66b4441 skip failing test suite (#192510) 2024-09-18 23:39:09 +10:00
Kibana Machine
fac293c873
[8.x] [Console] UX Improvements for phase 2 (#190698) (#193169) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Console] UX Improvements for phase 2
(#190698)](https://github.com/elastic/kibana/pull/190698)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Ignacio
Rivas","email":"rivasign@gmail.com"},"sourceCommit":{"committedDate":"2024-09-17T13:35:20Z","message":"[Console]
UX Improvements for phase 2
(#190698)","sha":"b3a1e5fb8f3bd6a05943ca3646186a0e3567cfe9","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:Console","Team:Kibana
Management","v9.0.0","backport:prev-minor","v8.16.0"],"title":"[Console]
UX Improvements for phase
2","number":190698,"url":"https://github.com/elastic/kibana/pull/190698","mergeCommit":{"message":"[Console]
UX Improvements for phase 2
(#190698)","sha":"b3a1e5fb8f3bd6a05943ca3646186a0e3567cfe9"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/190698","number":190698,"mergeCommit":{"message":"[Console]
UX Improvements for phase 2
(#190698)","sha":"b3a1e5fb8f3bd6a05943ca3646186a0e3567cfe9"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Ignacio Rivas <rivasign@gmail.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
 2024-09-18 01:22:58 -05:00
Kibana Machine
0be79333f8
[8.x] [Cloud] Add configuration for CSP value (#190491) (#192821) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Cloud] Add configuration for CSP value
(#190491)](https://github.com/elastic/kibana/pull/190491)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Jean-Louis
Leysens","email":"jeanlouis.leysens@elastic.co"},"sourceCommit":{"committedDate":"2024-09-13T08:55:36Z","message":"[Cloud]
Add configuration for CSP value (#190491)\n\n## Summary\r\n\r\nExposes
the CSP from the cloud setup plugin contract.\r\n\r\nRelated
https://github.com/elastic/kibana/issues/190023\r\n\r\n##
Notes\r\n\r\nIntended for cloud deployments, how/where will this config
value be set?\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are
not applicable to this PR.\r\n\r\n-
[x]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [x] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"b52695edfb15e555eedbe0be1ece4a779ddfbd97","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","v8.16.0"],"title":"[Cloud]
Add configuration for CSP
value","number":190491,"url":"https://github.com/elastic/kibana/pull/190491","mergeCommit":{"message":"[Cloud]
Add configuration for CSP value (#190491)\n\n## Summary\r\n\r\nExposes
the CSP from the cloud setup plugin contract.\r\n\r\nRelated
https://github.com/elastic/kibana/issues/190023\r\n\r\n##
Notes\r\n\r\nIntended for cloud deployments, how/where will this config
value be set?\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are
not applicable to this PR.\r\n\r\n-
[x]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [x] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"b52695edfb15e555eedbe0be1ece4a779ddfbd97"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/190491","number":190491,"mergeCommit":{"message":"[Cloud]
Add configuration for CSP value (#190491)\n\n## Summary\r\n\r\nExposes
the CSP from the cloud setup plugin contract.\r\n\r\nRelated
https://github.com/elastic/kibana/issues/190023\r\n\r\n##
Notes\r\n\r\nIntended for cloud deployments, how/where will this config
value be set?\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are
not applicable to this PR.\r\n\r\n-
[x]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [x] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"b52695edfb15e555eedbe0be1ece4a779ddfbd97"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Jean-Louis Leysens <jeanlouis.leysens@elastic.co>
 2024-09-13 05:28:12 -05:00
Catherine Liu
3d8fad56f2
[Dashboard] Remove library and drilldown notifications (#190797) 
## Summary

Pre-req for #182535.

We're removing the linked to library and drilldown notifications as part
of the panel hover actions redesign which gets rid of the title bar in
edit mode. We want to prevent panels from having a title bar when titles
are hidden and believe these notifications are no longer necessary. The
only notification retained is the panel filter notification.
 
<img width="421" alt="Screenshot 2024-08-20 at 6 34 16 AM"
src="https://github.com/user-attachments/assets/9f954a6f-3a70-43c9-a3c3-28f92f1efba8">
<img width="269" alt="Screenshot 2024-08-20 at 6 37 18 AM"
src="https://github.com/user-attachments/assets/b6c154d5-0b8c-4c8b-ac72-a190d03f8801">


I also did some cleanup and removed unused page objects from the vis,
dashboard, and discover functional tests.

### Checklist

Delete any items that are not applicable to this PR.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [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
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)


### Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to
identify risks that should be tested prior to the change/feature
release.

When forming the risk matrix, consider some of the following examples
and how they may potentially impact the change:

| Risk | Probability | Severity | Mitigation/Notes |

|---------------------------|-------------|----------|-------------------------|
| Multiple Spaces&mdash;unexpected behavior in non-default Kibana Space.
| Low | High | Integration tests will verify that all features are still
supported in non-default Kibana Space and when user switches between
spaces. |
| Multiple nodes&mdash;Elasticsearch polling might have race conditions
when multiple Kibana nodes are polling for the same tasks. | High | Low
| Tasks are idempotent, so executing them multiple times will not result
in logical error, but will degrade performance. To test for this case we
add plenty of unit tests around this logic and document manual testing
procedure. |
| Code should gracefully handle cases when feature X or plugin Y are
disabled. | Medium | High | Unit tests will verify that any feature flag
or plugin combination still results in our service operational. |
| [See more potential risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |


### For maintainers

- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2024-09-09 14:11:15 -07:00
Luke Elmers
b6287708f6
Adds AGPL 3.0 license (#192025) 
Updates files outside of x-pack to be triple-licensed under Elastic
License 2.0, AGPL 3.0, or SSPL 1.0.
 2024-09-06 19:02:41 -06:00
Zacqary Adam Xeper
ee28e20de8
[Embeddables Rebuild] Migrate Visualize (#183197) 
## Summary

Closes #174958

This migrates the Visualize embeddable to the new React Embeddable
framework.

Migrated:
- Edit visualization action
- Convert to lens action
- Extracting/injecting references on serialize and deserialize
- Inspector adapters
- Dashboard settings
- Drilldown support
- Timeslice/time slider support
- Custom time ranges

Also adds deprecation statements to legacy Embeddable factories

**In a second PR, we'll move the `embeddable` folder to
`legacy/embeddable` and rename `react_embeddable` to `embeddable`. I
don't know if git will be able to diff that change in a comprehensible
way in this PR, so I want to save it for the next one.**

### 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: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Devon Thomson <devon.thomson@elastic.co>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>
 2024-08-30 09:05:17 -06:00
Alejandro Fernández Haro
454be59c14
Flaky #187671 (#191542) 2024-08-28 17:23:42 -07:00
Patryk Kopyciński
2d1d592a3b
[react@18] Fix useCallback breaking type changes (#182344) 
## Summary

Prep work for React@18 bump
https://github.com/elastic/kibana/issues/138222

In React@18 `useCallback` types has changed that introduced breaking
changes:
https://github.com/DefinitelyTyped/DefinitelyTyped/issues/46691

Fixed using:

https://github.com/eps1lon/types-react-codemod?tab=readme-ov-file#usecallback-implicit-any

**Tried to do my best with fixing the types, but if you disagree or have
a better idea how it should be solved feel free to suggest changes or
commit directly to the branch 🙏**

---------

Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co>
Co-authored-by: Sébastien Loix <sabee77@gmail.com>
Co-authored-by: Nick Peihl <nick.peihl@elastic.co>
Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
Co-authored-by: Felix Stürmer <felix.stuermer@elastic.co>
Co-authored-by: nickofthyme <nicholas.partridge@elastic.co>
Co-authored-by: Davis McPhee <davis.mcphee@elastic.co>
Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com>
Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
Co-authored-by: Christos Nasikas <christos.nasikas@elastic.co>
Co-authored-by: Anton Dosov <anton.dosov@elastic.co>
 2024-08-28 16:33:35 +02:00
Tim Sullivan
dc7e3ec999
[EuiProvider / Functional tests] Check for EuiProvider Dev Warning (#189018) 
## Summary

Follows https://github.com/elastic/kibana/pull/184608
Closes https://github.com/elastic/kibana-team/issues/805


![image](https://github.com/user-attachments/assets/eaee5b81-c1e9-4e81-9018-db57652236dc)

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2024-08-26 15:08:32 -05:00
Larry Gregory
2ca2f2a4d7
Seal native prototypes on the server (#190716) 
## Summary

This PR
[seals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/seal)
`Object.prototype`, `String.prototype`, `Number.prototype`, and
`Function.prototype` on the Kibana server, which provides some measure
of protection against prototype pollution.

<details>
<summary>The Object.seal() static method seals an object.</summary>
**note** I currently have this marked as `backport:skip` to reduce the
risk of regressions in patch releases.

> The Object.seal() static method seals an object. Sealing an object
[prevents
extensions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/preventExtensions)
and makes existing properties non-configurable. A sealed object has a
fixed set of properties: new properties cannot be added, existing
properties cannot be removed, their enumerability and configurability
cannot be changed, and its prototype cannot be re-assigned. Values of
existing properties can still be changed as long as they are writable.
seal() returns the same object that was passed in.
</details>

-----

## Help, this broke something!

Please let us know by opening an issue. If you need to get your
environment up and running quickly, you can disable these protections by
setting the `KBN_UNSAFE_DISABLE_PROTOTYPE_HARDENING` environment
variable to any truthy value.

This may be interfering with normal functionality if you encounter an
error similar to:
> Cannot add property foo, object is not extensible

Where `foo` is some arbitrary string.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2024-08-26 08:33:03 -05:00
Dzmitry Lemechko
fa69337c94
[FTR] enable recommended mocha + no-floating-promises ESLint rules (#190690) 
## Summary

This PR enforces ESLint rules in FTR tests, in particular:
- `no-floating-promises` rule to catch unawaited Promises in
tests/services/page objects

_Why is it important?_
- Keep correct test execution order: cleanup code may run before the
async operation is completed, leading to unexpected behavior in
subsequent tests
- Accurate test results: If a test completes before an async operation
(e.g., API request) has finished, Mocha might report the test as passed
or failed based on incomplete context.
```
198:11  error  Promises must be awaited, end with a call to .catch, end with a call to .then
with a rejection handler or be explicitly marked as ignored with the `void` operator 
@typescript-eslint/no-floating-promises
```
<img width="716" alt="Screenshot 2024-08-20 at 14 04 43"
src="https://github.com/user-attachments/assets/9afffe4c-4b51-4790-964c-c44a76baed1e">

- recommended rules from
[eslint-mocha-plugin](https://www.npmjs.com/package/eslint-plugin-mocha)
including:
-
[no-async-describe](https://github.com/lo1tuma/eslint-plugin-mocha/blob/main/docs/rules/no-async-describe.md)
-
[no-identical-title.md](https://github.com/lo1tuma/eslint-plugin-mocha/blob/main/docs/rules/no-identical-title.md)
-
[no-sibling-hooks.md](https://github.com/lo1tuma/eslint-plugin-mocha/blob/main/docs/rules/no-sibling-hooks.md)
and others

Note for reviewers: some tests were skipped due to failures after
missing `await` was added. Most likely is a "false positive" case when
test is finished before async operation is actually completed. Please
work on fixing and re-enabling it

---------

Co-authored-by: Tiago Costa <tiago.costa@elastic.co>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2024-08-23 11:54:36 -05:00
Nick Partridge
94b657e6c9
Add 5s minRefreshInterval to timefilter with validation (#188881) 
Adds enforcement for the global time filter to limit the min refresh interval.
 2024-08-23 11:21:52 -05:00
Paulo Henrique
a28f2193bc
[Agentless API] Updating Agentless API URL and enablement flag (#190277) 
## Summary

It closes https://github.com/elastic/security-team/issues/10104

This PR addresses the necessary changes in Kibana to reflect the updated
agentless API settings in kibana.yml settings:

- **xpack.fleet.agentless.enabled: true**
Changing to use `xpack.fleet.agentless.enabled` as a Feature flag for
enabling agentless in ESS environments. (Serverless changes was out of
scope, so it is still using `xpack.fleet.enableExperimental` for now).
Also, this value will now be exposed to the client side instead of the
API URL (It closes
https://github.com/elastic/security-team/issues/10019).


- **xpack.fleet.agentless.api.url**
This setting will now include only the URL (without the basePath), so I
added a `prependAgentlessApiBasePathToEndpoint` helper function to
append the basePath with type support. Also this value will no longer be
exposed to the client side

### Additional changes

- This PR also modified the Agentless settings schema validation to be
optional (so it will only validate the types), as because of the nature
of how the `kibana.yml` will set the configuration as of
[this](https://github.com/elastic/cloud/pull/130314) PR, it might happen
that we will have partial settings, so changing the schema to optional
will prevent Kibana failing from starting due to incomplete agentless
settings. (It closes
https://github.com/elastic/security-team/issues/10189)

- Updated unit tests and FTR e2e config files to reflect the latest
changes
 2024-08-13 19:48:46 -05:00
Nick Partridge
2f9dca4b02
fix: kbn-config-schema tests for conditional config schemas (#190259) 2024-08-13 13:54:56 -05:00
Alejandro Fernández Haro
de6e45241f
Flaky #175531 - sort keys (#190157) 2024-08-08 15:35:35 -05:00
Sébastien Loix
03607ec7e0
[Stateful sidenav] Remove Launch Darkly feature flag (#189513) 2024-08-02 07:48:19 -05:00
Alejandro Fernández Haro
89f703f1c5
Flaky test #118488 (#189542) 2024-07-30 16:33:33 -05:00
Luke G
7db28682dd
[Security Solution] Support experimental features in timelines (#189028) 
## Summary

Adding generic support for experimental features in timelines

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2024-07-26 10:46:40 -05:00
Pierre Gayvallet
85a90a71e4
Add FTR tests for stream/buffer error responses (#188937) 
## Summary

Fix https://github.com/elastic/kibana/issues/56305
 2024-07-24 15:00:13 +02:00
Alejandro Fernández Haro
56fc5ce8e1
[Cloud] Extend metadata (#189001) 2024-07-24 14:10:28 +02:00
Kibana Machine
91ed11ac91 skip failing test suite (#118488) 2024-07-22 15:35:59 +02:00
Rachel Shen
f57d9c5f01
[Global Search] Limit characters for global search bar (#186560) 
## Summary

This PR limits the number of characters that can be input into the
global search bar. The character limit can be specified with the config
value `xpack.global_search_bar.input_max_limit` with a default of
`1000`. When an input that exceeds the configured character limit is
provided a descriptive visual notice is displayed to the user.

## Visual 
<img width="662" alt="Screenshot 2024-07-04 at 19 28 39"
src="cf30f589-fe65-40a9-b9c8-ce0f235d206e">


## How to test

- run the following command below in the browser console, which would
create a string that exceeds the configured default search character
limit and copy it to your clipboard
```ts
	copy(Array.from(new Array(1001)).reduce((acc) => acc+'a', ''))
```
- open up kibana, simply paste the value that should exist in your
clipboard in the global search input field and you should be presented
with a result similar to the image above.

---------

Co-authored-by: Eyo Okon Eyo <eyo.eyo@elastic.co>
 2024-07-11 07:50:20 -07:00
Gerard Soldevila
e524fb6324
Relocate usage-counters to dedicated index and split server Vs ui (#187064) 
## Summary

Part of https://github.com/elastic/kibana/issues/186530.

This PR sets the basis for allowing namespaced usage counters.
It relocates `usage-counters` SO type from `.kibana` to a dedicated
`.kibana_usage_counters`.

Furthermore, the original SO type is removed, and replaced by 2 separate
types:
* `server-counters`
* `ui-counters`

Note that these 2 steps are necessary if we want to leverage
`namespaces` property of the saved objects.
We can't currently update the `namespaceType: 'agnostic'` without
causing a migration.
Thus, these two types will be defined as `namespaceType: single`.

Up until now, UI counters were stored under a special `domainId:
uiCounter`.
This forced a workaround that consisted in storing `appName:eventName`
in the `counterName` property of the SO.
Having a dedicated SO type for them allows to store `appName` as
`domainId`, avoiding the need for a
[workaround](https://github.com/elastic/kibana/blob/main/src/plugins/usage_collection/common/ui_counters.ts).

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2024-07-05 21:18:36 +10:00
Kevin Lacabane
a493e4075b
[eem] rename asset_manager to entity_manager (#186617) 
## Summary

Renames the experimental asset_manager plugin (never
documented/officially released) into entity_manager. I've used `node
scripts/lint_ts_projects --fix` and `node scripts/lint_packages.js
--fix` to help with the procedure and also renamed manually the
asset_manager references left.

The change also removes the deprecated asset_manager code, including the
`assetManager.alphaEnabled` plugin configuration. This means
entityManager plugin will be enabled by default.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2024-06-26 14:25:32 +02:00
Elena Stoeva
781db4507d
[Index Management] Disable data stream stats in serverless (#186420) 
Closes https://github.com/elastic/kibana/issues/184671
Fixes https://github.com/elastic/kibana/issues/186245
Fixes https://github.com/elastic/kibana/issues/186243
Fixes https://github.com/elastic/kibana/issues/186242

## Summary

This PR disables the data stream stats API request in serverless and the
stats toggle in the Data stream list view. It adds a new config
`enableDataStreamStats` and removes the `enableDataStreamsStorageColumn`
one as it is now redundant (since the storage size property is part of
the data stream stats).

### How to test:

**In serverless:**
1. Start serverless Es and Kibana
2. Go to Stack Management -> Index Management and open the Data Streams
tab.
3. Verify that the stats toggle is not displayed and the data stream
detail panels don't include any of the stats (`storageSizeBytes` and
`maxTimeStamp`).

**In stateful:**
1. Start stateful Es and Kibana
2. Go to Stack Management -> Index Management and open the Data Streams
tab.
3. Verify that the stats toggle is displayed and switching it adds the
stats columns to the table.
4. Verify that the data stream detail panels include the stats.


<!--
### Checklist

Delete any items that are not applicable to this PR.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [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
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)


### Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to
identify risks that should be tested prior to the change/feature
release.

When forming the risk matrix, consider some of the following examples
and how they may potentially impact the change:

| Risk | Probability | Severity | Mitigation/Notes |

|---------------------------|-------------|----------|-------------------------|
| Multiple Spaces&mdash;unexpected behavior in non-default Kibana Space.
| Low | High | Integration tests will verify that all features are still
supported in non-default Kibana Space and when user switches between
spaces. |
| Multiple nodes&mdash;Elasticsearch polling might have race conditions
when multiple Kibana nodes are polling for the same tasks. | High | Low
| Tasks are idempotent, so executing them multiple times will not result
in logical error, but will degrade performance. To test for this case we
add plenty of unit tests around this logic and document manual testing
procedure. |
| Code should gracefully handle cases when feature X or plugin Y are
disabled. | Medium | High | Unit tests will verify that any feature flag
or plugin combination still results in our service operational. |
| [See more potential risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |


### For maintainers

- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
-->
 2024-06-21 13:45:23 -07:00
seanrathier
9c1799cd0d
[Cloud Security] [Fleet] Adding new agentless-api url config for Fleet plugin (#186338) 2024-06-21 15:12:49 -04:00
Davis McPhee
57891ff353
[Discover] Add support for contextual awareness functional tests (#185905) 
## Summary

This PR adds functional test support for the Discover contextual
awareness framework, and adds tests for the initial `getCellRenderers`
extension point using example profiles.

To support this, this PR introduces a new YAML setting called
`discover.experimental.enabledProfiles` which can be used to selectively
enable profiles both for functional testing and demoing WIP profiles
that aren't yet ready for GA.

Example usage:
```yml
discover.experimental.enabledProfiles: ['example-root-profile', 'example-data-source-profile', 'example-document-profile']
```

Flaky test runs:
- Stateful x50:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6304
- Serverless Observability x50:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6305
- Serverless Search x50:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6306
- Serverless Security x50:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6307

Resolves #184699.

### Checklist

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [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
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)

### For maintainers

- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
 2024-06-19 14:17:26 -03:00