# Backport
This will backport the following commits from `main` to `8.x`:
- [SKA: Update broken references and URLs
(#206836)](https://github.com/elastic/kibana/pull/206836)
<!--- Backport version: 9.6.4 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)
<!--BACKPORT [{"author":{"name":"Gerard
Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-01-28T03:32:48Z","message":"SKA:
Update broken references and URLs (#206836)\n\n## Summary\r\n\r\nUpdates
a number of broken file references and broken
links.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Alejandro Fernández Haro
<afharo@gmail.com>","sha":"fb26c1c683453faa7f8218df094f90d9ad070a23","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Feature:ExpressionLanguage","release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","Team:obs-ux-management"],"title":"SKA:
Update broken references and
URLs","number":206836,"url":"https://github.com/elastic/kibana/pull/206836","mergeCommit":{"message":"SKA:
Update broken references and URLs (#206836)\n\n## Summary\r\n\r\nUpdates
a number of broken file references and broken
links.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Alejandro Fernández Haro
<afharo@gmail.com>","sha":"fb26c1c683453faa7f8218df094f90d9ad070a23"}},"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/206836","number":206836,"mergeCommit":{"message":"SKA:
Update broken references and URLs (#206836)\n\n## Summary\r\n\r\nUpdates
a number of broken file references and broken
links.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Alejandro Fernández Haro
<afharo@gmail.com>","sha":"fb26c1c683453faa7f8218df094f90d9ad070a23"}}]}]
BACKPORT-->
# Backport
This will backport the following commits from `main` to `8.x`:
- [Fix typo in documentation
(#204814)](https://github.com/elastic/kibana/pull/204814)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"Katerina","email":"aikaterini.patticha@elastic.co"},"sourceCommit":{"committedDate":"2024-12-19T00:20:59Z","message":"Fix
typo in documentation (#204814)\n\nFix typo introduced in
https://github.com/elastic/kibana/pull/204179#pullrequestreview-2512105404","sha":"7d4bf216ab59258a1d26dfd6c240978b00027c87","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":"Fix
typo in
documentation","number":204814,"url":"https://github.com/elastic/kibana/pull/204814","mergeCommit":{"message":"Fix
typo in documentation (#204814)\n\nFix typo introduced in
https://github.com/elastic/kibana/pull/204179#pullrequestreview-2512105404","sha":"7d4bf216ab59258a1d26dfd6c240978b00027c87"}},"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/204814","number":204814,"mergeCommit":{"message":"Fix
typo in documentation (#204814)\n\nFix typo introduced in
https://github.com/elastic/kibana/pull/204179#pullrequestreview-2512105404","sha":"7d4bf216ab59258a1d26dfd6c240978b00027c87"}}]}]
BACKPORT-->
Co-authored-by: Katerina <aikaterini.patticha@elastic.co>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[Performance] Update `onPageReady` documentation
(#204179)](https://github.com/elastic/kibana/pull/204179)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"Katerina","email":"aikaterini.patticha@elastic.co"},"sourceCommit":{"committedDate":"2024-12-18T15:06:54Z","message":"[Performance]
Update `onPageReady` documentation (#204179)\n\n## Summary\r\nRelated to
this: https://github.com/elastic/kibana/pull/202889\r\n\r\nUpdate the
documentation with the recent
changes","sha":"860d5b6b3599dcdf1a090923224b5c315156c1a5","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":"[Performance]
Update `onPageReady`
documentation","number":204179,"url":"https://github.com/elastic/kibana/pull/204179","mergeCommit":{"message":"[Performance]
Update `onPageReady` documentation (#204179)\n\n## Summary\r\nRelated to
this: https://github.com/elastic/kibana/pull/202889\r\n\r\nUpdate the
documentation with the recent
changes","sha":"860d5b6b3599dcdf1a090923224b5c315156c1a5"}},"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/204179","number":204179,"mergeCommit":{"message":"[Performance]
Update `onPageReady` documentation (#204179)\n\n## Summary\r\nRelated to
this: https://github.com/elastic/kibana/pull/202889\r\n\r\nUpdate the
documentation with the recent
changes","sha":"860d5b6b3599dcdf1a090923224b5c315156c1a5"}}]}]
BACKPORT-->
Co-authored-by: Katerina <aikaterini.patticha@elastic.co>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[Authz] Operator privileges
(#196583)](https://github.com/elastic/kibana/pull/196583)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Elena
Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-12T22:55:04Z","message":"[Authz]
Operator privileges (#196583)\n\n## Summary\r\n\r\nThis PR adds support
for explicit indication whether endpoint is\r\nrestricted to operator
only users.\r\n\r\n### Context\r\n1. If user has [all
operator\r\nprivileges](https://github.com/elastic/elasticsearch/blob/main/x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/operator/DefaultOperatorOnlyRegistry.java#L35-#L53)\r\ngranted,
but is not listed as operator in `operator_users.yml`, ES would\r\nthrow
an unauthorized error.\r\n2. If user is listed as operator in
`operator_users.yml`, but doesn't\r\nhave necessary privileges granted,
ES would throw an unauthorized error.\r\n3. It’s not possible to
determine if a user is operator via any ES API,\r\ni.e.
`_has_privileges`.\r\n4. If operator privileges are disabled we skip the
the check for it,\r\nthat's why we require to explicitly specify
additional privileges to\r\nensure that the route is protected even when
operator privileges are\r\ndisabled.\r\n\r\n### Checklist\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\r\n\r\n__Relates:
https://github.com/elastic/kibana/issues/196271__\r\n\r\n### How to
test\r\n\r\n1. Add your user to the operators
list\r\n1bd8144924/packages/kbn-es/src/serverless_resources/operator_users.yml (L4)\r\nor
use existing user from the list to log in.\r\n2. Run ES and Kibana
serverless\r\n3. Change any endpoint or create a new one with the
following security\r\nconfig\r\n```\r\n security: {\r\n authz: {\r\n
requiredPrivileges: [ReservedPrivilegesSet.operator],\r\n },\r\n
},\r\n```\r\n4. Check with enabled and disabled operator privileges
(set\r\n`xpack.security.operator_privileges.enabled`)\r\n\r\n## Release
Note\r\nAdded support for explicit indication whether endpoint is
restricted to\r\noperator only users at the route definition
level.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"52dd7e17c4ee1bcada352b142532ca534002e8d5","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Security","Feature:Security/Authorization","v9.0.0","backport:prev-minor"],"title":"[Authz]
Operator
privileges","number":196583,"url":"https://github.com/elastic/kibana/pull/196583","mergeCommit":{"message":"[Authz]
Operator privileges (#196583)\n\n## Summary\r\n\r\nThis PR adds support
for explicit indication whether endpoint is\r\nrestricted to operator
only users.\r\n\r\n### Context\r\n1. If user has [all
operator\r\nprivileges](https://github.com/elastic/elasticsearch/blob/main/x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/operator/DefaultOperatorOnlyRegistry.java#L35-#L53)\r\ngranted,
but is not listed as operator in `operator_users.yml`, ES would\r\nthrow
an unauthorized error.\r\n2. If user is listed as operator in
`operator_users.yml`, but doesn't\r\nhave necessary privileges granted,
ES would throw an unauthorized error.\r\n3. It’s not possible to
determine if a user is operator via any ES API,\r\ni.e.
`_has_privileges`.\r\n4. If operator privileges are disabled we skip the
the check for it,\r\nthat's why we require to explicitly specify
additional privileges to\r\nensure that the route is protected even when
operator privileges are\r\ndisabled.\r\n\r\n### Checklist\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\r\n\r\n__Relates:
https://github.com/elastic/kibana/issues/196271__\r\n\r\n### How to
test\r\n\r\n1. Add your user to the operators
list\r\n1bd8144924/packages/kbn-es/src/serverless_resources/operator_users.yml (L4)\r\nor
use existing user from the list to log in.\r\n2. Run ES and Kibana
serverless\r\n3. Change any endpoint or create a new one with the
following security\r\nconfig\r\n```\r\n security: {\r\n authz: {\r\n
requiredPrivileges: [ReservedPrivilegesSet.operator],\r\n },\r\n
},\r\n```\r\n4. Check with enabled and disabled operator privileges
(set\r\n`xpack.security.operator_privileges.enabled`)\r\n\r\n## Release
Note\r\nAdded support for explicit indication whether endpoint is
restricted to\r\noperator only users at the route definition
level.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"52dd7e17c4ee1bcada352b142532ca534002e8d5"}},"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/196583","number":196583,"mergeCommit":{"message":"[Authz]
Operator privileges (#196583)\n\n## Summary\r\n\r\nThis PR adds support
for explicit indication whether endpoint is\r\nrestricted to operator
only users.\r\n\r\n### Context\r\n1. If user has [all
operator\r\nprivileges](https://github.com/elastic/elasticsearch/blob/main/x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/operator/DefaultOperatorOnlyRegistry.java#L35-#L53)\r\ngranted,
but is not listed as operator in `operator_users.yml`, ES would\r\nthrow
an unauthorized error.\r\n2. If user is listed as operator in
`operator_users.yml`, but doesn't\r\nhave necessary privileges granted,
ES would throw an unauthorized error.\r\n3. It’s not possible to
determine if a user is operator via any ES API,\r\ni.e.
`_has_privileges`.\r\n4. If operator privileges are disabled we skip the
the check for it,\r\nthat's why we require to explicitly specify
additional privileges to\r\nensure that the route is protected even when
operator privileges are\r\ndisabled.\r\n\r\n### Checklist\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\r\n\r\n__Relates:
https://github.com/elastic/kibana/issues/196271__\r\n\r\n### How to
test\r\n\r\n1. Add your user to the operators
list\r\n1bd8144924/packages/kbn-es/src/serverless_resources/operator_users.yml (L4)\r\nor
use existing user from the list to log in.\r\n2. Run ES and Kibana
serverless\r\n3. Change any endpoint or create a new one with the
following security\r\nconfig\r\n```\r\n security: {\r\n authz: {\r\n
requiredPrivileges: [ReservedPrivilegesSet.operator],\r\n },\r\n
},\r\n```\r\n4. Check with enabled and disabled operator privileges
(set\r\n`xpack.security.operator_privileges.enabled`)\r\n\r\n## Release
Note\r\nAdded support for explicit indication whether endpoint is
restricted to\r\noperator only users at the route definition
level.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"52dd7e17c4ee1bcada352b142532ca534002e8d5"}}]}]
BACKPORT-->
Co-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[Docs] Update feature privilege docs to reflect new route
authorization (#201017)](https://github.com/elastic/kibana/pull/201017)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"Sid","email":"siddharthmantri1@gmail.com"},"sourceCommit":{"committedDate":"2024-11-20T20:52:58Z","message":"[Docs]
Update feature privilege docs to reflect new route authorization
(#201017)\n\n## Summary\r\n\r\nUpdates developer documentation on
Feature privileges to reflect changes\r\nto Route
Authorization.\r\n\r\n\r\n### Screenshots\r\nBefore\r\n<img
width=\"400\" alt=\"Screenshot 2024-11-20 at 18 52
02\"\r\nsrc=\"https://github.com/user-attachments/assets/0bb01bd0-e41a-48ee-bcaf-bd4119037f1b\">\r\n\r\nAfter\r\n<img
width=\"400\" alt=\"Screenshot 2024-11-20 at 18 49
26\"\r\nsrc=\"https://github.com/user-attachments/assets/2d5712ce-c277-4ecd-831e-750df8309933\">\r\n\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]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or
tutorials","sha":"4ffdb35b14c1a19cf0ade972b198a6e6e7f06ba5","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","v9.0.0","docs","DevDocs","backport:prev-minor","v8.17.0"],"title":"[Docs]
Update feature privilege docs to reflect new route
authorization","number":201017,"url":"https://github.com/elastic/kibana/pull/201017","mergeCommit":{"message":"[Docs]
Update feature privilege docs to reflect new route authorization
(#201017)\n\n## Summary\r\n\r\nUpdates developer documentation on
Feature privileges to reflect changes\r\nto Route
Authorization.\r\n\r\n\r\n### Screenshots\r\nBefore\r\n<img
width=\"400\" alt=\"Screenshot 2024-11-20 at 18 52
02\"\r\nsrc=\"https://github.com/user-attachments/assets/0bb01bd0-e41a-48ee-bcaf-bd4119037f1b\">\r\n\r\nAfter\r\n<img
width=\"400\" alt=\"Screenshot 2024-11-20 at 18 49
26\"\r\nsrc=\"https://github.com/user-attachments/assets/2d5712ce-c277-4ecd-831e-750df8309933\">\r\n\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]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or
tutorials","sha":"4ffdb35b14c1a19cf0ade972b198a6e6e7f06ba5"}},"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/201017","number":201017,"mergeCommit":{"message":"[Docs]
Update feature privilege docs to reflect new route authorization
(#201017)\n\n## Summary\r\n\r\nUpdates developer documentation on
Feature privileges to reflect changes\r\nto Route
Authorization.\r\n\r\n\r\n### Screenshots\r\nBefore\r\n<img
width=\"400\" alt=\"Screenshot 2024-11-20 at 18 52
02\"\r\nsrc=\"https://github.com/user-attachments/assets/0bb01bd0-e41a-48ee-bcaf-bd4119037f1b\">\r\n\r\nAfter\r\n<img
width=\"400\" alt=\"Screenshot 2024-11-20 at 18 49
26\"\r\nsrc=\"https://github.com/user-attachments/assets/2d5712ce-c277-4ecd-831e-750df8309933\">\r\n\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]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or
tutorials","sha":"4ffdb35b14c1a19cf0ade972b198a6e6e7f06ba5"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Sid <siddharthmantri1@gmail.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [Enhance documentation on accessing hidden SO types
(#199046)](https://github.com/elastic/kibana/pull/199046)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Christiane (Tina)
Heiligers","email":"christiane.heiligers@elastic.co"},"sourceCommit":{"committedDate":"2024-11-06T01:51:45Z","message":"Enhance
documentation on accessing hidden SO types (#199046)\n\nSaved objects
declared as `hidden` can only be accessed with a client\r\nthat
explicitly includes hidden types.\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: Alejandro Fernández
Haro
<afharo@gmail.com>","sha":"73f31549cd0ae6c4aa5cc505907e455d16307190","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Feature:Saved
Objects","release_note:skip","v9.0.0","DevDocs","backport:prev-minor","v8.17.0"],"title":"Enhance
documentation on accessing hidden SO
types","number":199046,"url":"https://github.com/elastic/kibana/pull/199046","mergeCommit":{"message":"Enhance
documentation on accessing hidden SO types (#199046)\n\nSaved objects
declared as `hidden` can only be accessed with a client\r\nthat
explicitly includes hidden types.\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: Alejandro Fernández
Haro
<afharo@gmail.com>","sha":"73f31549cd0ae6c4aa5cc505907e455d16307190"}},"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/199046","number":199046,"mergeCommit":{"message":"Enhance
documentation on accessing hidden SO types (#199046)\n\nSaved objects
declared as `hidden` can only be accessed with a client\r\nthat
explicitly includes hidden types.\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: Alejandro Fernández
Haro
<afharo@gmail.com>","sha":"73f31549cd0ae6c4aa5cc505907e455d16307190"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Christiane (Tina) Heiligers <christiane.heiligers@elastic.co>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[Docs] Security Route Configuration
(#193994)](https://github.com/elastic/kibana/pull/193994)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Elena
Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-22T11:30:53Z","message":"[Docs]
Security Route Configuration (#193994)\n\n## Summary\r\n\r\nAdded
documentation for the security route configuration.\r\n\r\n\r\n###
Checklist\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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"300678ca85209159c9c2cbb5a92c0b49dc0984d7","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","Feature:Security/Authorization","v9.0.0","DevDocs","backport:prev-minor"],"title":"[Docs]
Security Route
Configuration","number":193994,"url":"https://github.com/elastic/kibana/pull/193994","mergeCommit":{"message":"[Docs]
Security Route Configuration (#193994)\n\n## Summary\r\n\r\nAdded
documentation for the security route configuration.\r\n\r\n\r\n###
Checklist\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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"300678ca85209159c9c2cbb5a92c0b49dc0984d7"}},"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/193994","number":193994,"mergeCommit":{"message":"[Docs]
Security Route Configuration (#193994)\n\n## Summary\r\n\r\nAdded
documentation for the security route configuration.\r\n\r\n\r\n###
Checklist\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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"300678ca85209159c9c2cbb5a92c0b49dc0984d7"}}]}]
BACKPORT-->
Co-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[Lens] fit line charts by default
(#196184)](https://github.com/elastic/kibana/pull/196184)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Marco
Vettorello","email":"marco.vettorello@elastic.co"},"sourceCommit":{"committedDate":"2024-10-21T13:05:02Z","message":"[Lens]
fit line charts by default (#196184)\n\n## Summary\r\n\r\nEvery line
charts are now interpolated by default with a
linear\r\ninterpolation.\r\n\r\nSolves the second task
of\r\n[#186076](https://github.com/elastic/kibana/issues/186076)\r\n\r\nfix
[#186076](https://github.com/elastic/kibana/issues/186076)\r\n\r\nbefore:\r\n<img
width=\"816\" alt=\"Screenshot 2024-10-17 at 16 25
47\"\r\nsrc=\"https://github.com/user-attachments/assets/3b14c80b-deef-4d8d-9d5b-e118619e31cb\">\r\n\r\n\r\nafter:\r\n<img
width=\"814\" alt=\"Screenshot 2024-10-17 at 16 25
56\"\r\nsrc=\"https://github.com/user-attachments/assets/45788530-aeb6-4851-ac1e-c53efcd73068\">\r\n\r\n##
Release note\r\nNewly and default configured Lens line charts are now
interpolated by\r\ndefault with a straight Linear
interpolation.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>","sha":"5fe8aad89d59726060ba860d2f0692ddb3ca5ffa","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","enhancement","Feature:Lens","v9.0.0","apm:review","backport:version","v8.17.0"],"title":"[Lens]
fit line charts by
default","number":196184,"url":"https://github.com/elastic/kibana/pull/196184","mergeCommit":{"message":"[Lens]
fit line charts by default (#196184)\n\n## Summary\r\n\r\nEvery line
charts are now interpolated by default with a
linear\r\ninterpolation.\r\n\r\nSolves the second task
of\r\n[#186076](https://github.com/elastic/kibana/issues/186076)\r\n\r\nfix
[#186076](https://github.com/elastic/kibana/issues/186076)\r\n\r\nbefore:\r\n<img
width=\"816\" alt=\"Screenshot 2024-10-17 at 16 25
47\"\r\nsrc=\"https://github.com/user-attachments/assets/3b14c80b-deef-4d8d-9d5b-e118619e31cb\">\r\n\r\n\r\nafter:\r\n<img
width=\"814\" alt=\"Screenshot 2024-10-17 at 16 25
56\"\r\nsrc=\"https://github.com/user-attachments/assets/45788530-aeb6-4851-ac1e-c53efcd73068\">\r\n\r\n##
Release note\r\nNewly and default configured Lens line charts are now
interpolated by\r\ndefault with a straight Linear
interpolation.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>","sha":"5fe8aad89d59726060ba860d2f0692ddb3ca5ffa"}},"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/196184","number":196184,"mergeCommit":{"message":"[Lens]
fit line charts by default (#196184)\n\n## Summary\r\n\r\nEvery line
charts are now interpolated by default with a
linear\r\ninterpolation.\r\n\r\nSolves the second task
of\r\n[#186076](https://github.com/elastic/kibana/issues/186076)\r\n\r\nfix
[#186076](https://github.com/elastic/kibana/issues/186076)\r\n\r\nbefore:\r\n<img
width=\"816\" alt=\"Screenshot 2024-10-17 at 16 25
47\"\r\nsrc=\"https://github.com/user-attachments/assets/3b14c80b-deef-4d8d-9d5b-e118619e31cb\">\r\n\r\n\r\nafter:\r\n<img
width=\"814\" alt=\"Screenshot 2024-10-17 at 16 25
56\"\r\nsrc=\"https://github.com/user-attachments/assets/45788530-aeb6-4851-ac1e-c53efcd73068\">\r\n\r\n##
Release note\r\nNewly and default configured Lens line charts are now
interpolated by\r\ndefault with a straight Linear
interpolation.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>","sha":"5fe8aad89d59726060ba860d2f0692ddb3ca5ffa"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[dev docs] Add recently viewed docs
(#195001)](https://github.com/elastic/kibana/pull/195001)
<!--- 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-10T14:16:52Z","message":"[dev
docs] Add recently viewed docs (#195001)\n\n## Summary\r\n\r\nAdd
Recently Viewed dev docs\r\n\r\n---------\r\n\r\nCo-authored-by: Tim
Sullivan <tsullivan@users.noreply.github.com>\r\nCo-authored-by: Clint
Andrew Hall
<clint@clintandrewhall.com>","sha":"129c0a1e7f716985deffef68371d21a52c8f1c3c","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","v9.0.0","Team:SharedUX","backport:prev-minor"],"title":"[dev
docs] Add recently viewed
docs","number":195001,"url":"https://github.com/elastic/kibana/pull/195001","mergeCommit":{"message":"[dev
docs] Add recently viewed docs (#195001)\n\n## Summary\r\n\r\nAdd
Recently Viewed dev docs\r\n\r\n---------\r\n\r\nCo-authored-by: Tim
Sullivan <tsullivan@users.noreply.github.com>\r\nCo-authored-by: Clint
Andrew Hall
<clint@clintandrewhall.com>","sha":"129c0a1e7f716985deffef68371d21a52c8f1c3c"}},"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/195001","number":195001,"mergeCommit":{"message":"[dev
docs] Add recently viewed docs (#195001)\n\n## Summary\r\n\r\nAdd
Recently Viewed dev docs\r\n\r\n---------\r\n\r\nCo-authored-by: Tim
Sullivan <tsullivan@users.noreply.github.com>\r\nCo-authored-by: Clint
Andrew Hall
<clint@clintandrewhall.com>","sha":"129c0a1e7f716985deffef68371d21a52c8f1c3c"}}]}]
BACKPORT-->
Co-authored-by: Anton Dosov <anton.dosov@elastic.co>
# Backport
This will backport the following commits from `main` to `8.x`:
- [Fix dev docs
(#194229)](https://github.com/elastic/kibana/pull/194229)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Brandon
Morelli","email":"brandon.morelli@elastic.co"},"sourceCommit":{"committedDate":"2024-09-26T21:32:03Z","message":"Fix
dev docs
(#194229)\n\n`kibDevTutorialsServerlessProjectNavigation`\r\nwas changed
to\r\n`kibDevTutorialsSolutionNavigation`\r\nin\r\nhttps://github.com/elastic/kibana/pull/193988\r\n\r\nbut
they missed one. This PR fixes the failing docs.elastic.dev
build.","sha":"4bebd2539f59b400456a2f25d59c038c87563181","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","v8.16.0"],"title":"Fix
dev
docs","number":194229,"url":"https://github.com/elastic/kibana/pull/194229","mergeCommit":{"message":"Fix
dev docs
(#194229)\n\n`kibDevTutorialsServerlessProjectNavigation`\r\nwas changed
to\r\n`kibDevTutorialsSolutionNavigation`\r\nin\r\nhttps://github.com/elastic/kibana/pull/193988\r\n\r\nbut
they missed one. This PR fixes the failing docs.elastic.dev
build.","sha":"4bebd2539f59b400456a2f25d59c038c87563181"}},"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/194229","number":194229,"mergeCommit":{"message":"Fix
dev docs
(#194229)\n\n`kibDevTutorialsServerlessProjectNavigation`\r\nwas changed
to\r\n`kibDevTutorialsSolutionNavigation`\r\nin\r\nhttps://github.com/elastic/kibana/pull/193988\r\n\r\nbut
they missed one. This PR fixes the failing docs.elastic.dev
build.","sha":"4bebd2539f59b400456a2f25d59c038c87563181"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co>
# Backport
This will backport the following commits from `main` to `8.x`:
- [Add dependency docs
(#194333)](https://github.com/elastic/kibana/pull/194333)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Larry
Gregory","email":"larry.gregory@elastic.co"},"sourceCommit":{"committedDate":"2024-10-02T11:55:32Z","message":"Add
dependency docs (#194333)\n\n## Summary\r\n\r\nAdds and re-organizes
documentation for using third-party
dependencies.","sha":"8e21442caa8e93ab85aed64c102f972985f96ab3","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","v9.0.0","DevDocs","backport:all-open"],"title":"Add
dependency
docs","number":194333,"url":"https://github.com/elastic/kibana/pull/194333","mergeCommit":{"message":"Add
dependency docs (#194333)\n\n## Summary\r\n\r\nAdds and re-organizes
documentation for using third-party
dependencies.","sha":"8e21442caa8e93ab85aed64c102f972985f96ab3"}},"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/194333","number":194333,"mergeCommit":{"message":"Add
dependency docs (#194333)\n\n## Summary\r\n\r\nAdds and re-organizes
documentation for using third-party
dependencies.","sha":"8e21442caa8e93ab85aed64c102f972985f96ab3"}}]}]
BACKPORT-->
Co-authored-by: Larry Gregory <larry.gregory@elastic.co>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[performance] support triggering subset of journeys against KIbana PR
in CI (#193175)](https://github.com/elastic/kibana/pull/193175)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2024-09-18T12:53:02Z","message":"[performance]
support triggering subset of journeys against KIbana PR in CI
(#193175)\n\n## Summary\r\n\r\nIt’s common request for Dev teams to run
specific journeys on a PR to\r\ncompare performance metrics against the
`main` branch. These requests\r\nusually focus on a particular area,
such as the Dashboard or Discover\r\napp.\r\n\r\nTo streamline the
process, this PR groups relevant journeys into\r\ncategories that can be
triggered through an environment variable. For\r\nexample, setting
`JOURNEYS_GROUP=dashboard` will execute only the
three\r\ndashboard-specific journeys, which are (usually) sufficient
for\r\nevaluating the performance impact of code changes within the
Dashboard\r\napp.\r\n\r\nCurrent Process for Triggering Performance
Builds:\r\n- Create a new
kibana-single-user-performance\r\n[build](https://buildkite.com/elastic/kibana-single-user-performance#new)\r\n-
Provide the following arguments:\r\n\r\nBranch:
`refs/pull/<PR_number>/head`\r\nUnder Options, set the environment
variable:\r\n`JOURNEYS_GROUP=<group_name>`\r\n\r\nCurrently supported
journey groups:\r\n- kibanaStartAndLoad\r\n- crud\r\n- dashboard\r\n-
discover\r\n- maps\r\n- ml\r\n\r\n[Build
example\r\n\r\n](https://buildkite.com/elastic/kibana-single-user-performance/builds/14427)\r\nEach
group focuses on a specific set of journeys tied to its
respective\r\narea in Kibana, allowing for more targeted performance
testing. Since\r\nrunning group takes ~5-10 min on bare metal worker, it
should not delay\r\nthe regular (every 3h) runs against `main`
branch\r\n\r\n\r\ntest locally with `node scripts/run_performance.js
--group
<group_name>`","sha":"f5975d28fa06d6de6193d5e518084c45c65b5aed","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","v8.16.0","backport:version"],"title":"[performance]
support triggering subset of journeys against KIbana PR in
CI","number":193175,"url":"https://github.com/elastic/kibana/pull/193175","mergeCommit":{"message":"[performance]
support triggering subset of journeys against KIbana PR in CI
(#193175)\n\n## Summary\r\n\r\nIt’s common request for Dev teams to run
specific journeys on a PR to\r\ncompare performance metrics against the
`main` branch. These requests\r\nusually focus on a particular area,
such as the Dashboard or Discover\r\napp.\r\n\r\nTo streamline the
process, this PR groups relevant journeys into\r\ncategories that can be
triggered through an environment variable. For\r\nexample, setting
`JOURNEYS_GROUP=dashboard` will execute only the
three\r\ndashboard-specific journeys, which are (usually) sufficient
for\r\nevaluating the performance impact of code changes within the
Dashboard\r\napp.\r\n\r\nCurrent Process for Triggering Performance
Builds:\r\n- Create a new
kibana-single-user-performance\r\n[build](https://buildkite.com/elastic/kibana-single-user-performance#new)\r\n-
Provide the following arguments:\r\n\r\nBranch:
`refs/pull/<PR_number>/head`\r\nUnder Options, set the environment
variable:\r\n`JOURNEYS_GROUP=<group_name>`\r\n\r\nCurrently supported
journey groups:\r\n- kibanaStartAndLoad\r\n- crud\r\n- dashboard\r\n-
discover\r\n- maps\r\n- ml\r\n\r\n[Build
example\r\n\r\n](https://buildkite.com/elastic/kibana-single-user-performance/builds/14427)\r\nEach
group focuses on a specific set of journeys tied to its
respective\r\narea in Kibana, allowing for more targeted performance
testing. Since\r\nrunning group takes ~5-10 min on bare metal worker, it
should not delay\r\nthe regular (every 3h) runs against `main`
branch\r\n\r\n\r\ntest locally with `node scripts/run_performance.js
--group
<group_name>`","sha":"f5975d28fa06d6de6193d5e518084c45c65b5aed"}},"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/193175","number":193175,"mergeCommit":{"message":"[performance]
support triggering subset of journeys against KIbana PR in CI
(#193175)\n\n## Summary\r\n\r\nIt’s common request for Dev teams to run
specific journeys on a PR to\r\ncompare performance metrics against the
`main` branch. These requests\r\nusually focus on a particular area,
such as the Dashboard or Discover\r\napp.\r\n\r\nTo streamline the
process, this PR groups relevant journeys into\r\ncategories that can be
triggered through an environment variable. For\r\nexample, setting
`JOURNEYS_GROUP=dashboard` will execute only the
three\r\ndashboard-specific journeys, which are (usually) sufficient
for\r\nevaluating the performance impact of code changes within the
Dashboard\r\napp.\r\n\r\nCurrent Process for Triggering Performance
Builds:\r\n- Create a new
kibana-single-user-performance\r\n[build](https://buildkite.com/elastic/kibana-single-user-performance#new)\r\n-
Provide the following arguments:\r\n\r\nBranch:
`refs/pull/<PR_number>/head`\r\nUnder Options, set the environment
variable:\r\n`JOURNEYS_GROUP=<group_name>`\r\n\r\nCurrently supported
journey groups:\r\n- kibanaStartAndLoad\r\n- crud\r\n- dashboard\r\n-
discover\r\n- maps\r\n- ml\r\n\r\n[Build
example\r\n\r\n](https://buildkite.com/elastic/kibana-single-user-performance/builds/14427)\r\nEach
group focuses on a specific set of journeys tied to its
respective\r\narea in Kibana, allowing for more targeted performance
testing. Since\r\nrunning group takes ~5-10 min on bare metal worker, it
should not delay\r\nthe regular (every 3h) runs against `main`
branch\r\n\r\n\r\ntest locally with `node scripts/run_performance.js
--group
<group_name>`","sha":"f5975d28fa06d6de6193d5e518084c45c65b5aed"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
## Summary
As titled. This PR outlines several use cases around plugin optimization
that can be helpful to engineers. This PR is part of a series, but
divided to make review easier.
It also reworks the navigation a bit to make the optimization section a
bit more clear.
## Summary
- Closeselastic/kibana-operations#101
This PR adds a [Dev Container](https://containers.dev/) to utilize for
Kibana local development in an isolated environment. The original
intention was to create a local environment for FIPS development because
setting up Kibana in FIPS mode is complicated and has the potential to
break the user's OS. However, it has been altered to allow for general
development if an engineer chooses as well. The idea is for this be a
cost efficient replacement for
[kibana-remote-dev](https://github.com/elastic/kibana-remote-dev)
eventually.
### Testing
- In VS Code you should be able to use the `Dev Containers: Clone GitHub
Pull Request in Named Container Volume...` command from the Command
Palette (F1) to easily test this PR.
- See the
[docs](bd125fc230/dev_docs/getting_started/setting_up_a_development_env.mdx (using-the-kibana-dev-container-optional))
for additional information on setting up the Dev Container.
### Bazel
I tried many different solutions to copy the local Bazel cache into the
container to speed up bootstrap, but it either would break Bazel or
didn't provide any meaningful boost in performance. I opted to forgo
keeping it in this PR due to the complexity and since we're planning to
phase out Bazel in the future anyways.
Closes#176097
## Summary
Adds 'Key concepts' developer documentation for Encrypted Saved Objects,
covering the basic theory, usage, and maintenance for encrypted saved
objects in Kibana.
Paired with @ThomThomson to expand Embeddable documentation with
"Guiding principles" and "Best practices"
PR also moves overview to src/plugins/embeddables/README.md. Then, this
markdown is displayed in the embeddable example application as well.
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Devon Thomson <devon.thomson@elastic.co>
Having the same thing in multiple places is confusing and hard to
maintain. Embeddable documentation is exposed via developer examples.
This PR removes embeddable documentation in README and dev-docs and
points those locations to the single location for embeddable
documenation.
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Added documentation explaining how SO migrations on serverless work
## Preview
<img width="741" alt="Screenshot 2024-03-22 at 16 15 13"
src="2217c01f-8447-4f22-a782-a07ff221aa42">
## Summary
For ES|QL charts the formula api should be redundant. This is going to
make the api lighter as there is no need to import the lens plugin if
you want to use the builder to create ES|QL charts.
## Summary
Moving synthtrace clients init inside kbn-journeys:
esArchiver does not always solve the issue with data generation. We
already have afew journeys using Synthtrace instead and expect more to
come.
In order to simplify the process of creating new journeys, this PR moves
Synthtrace client initialisation into kbn-journey package and exposes a
way to define client type, generator function & its input arguments:
```
import { Journey, SynthtraceOptions } from '@kbn/journeys';
import { subj } from '@kbn/test-subj-selector';
import { generateApmData } from '../synthtrace_data/apm_data';
export const journey = new Journey({
synthtrace: {
type: 'apm',
generator: generateApmData,
options: {
from: new Date(Date.now() - 1000 * 60 * 15),
to: new Date(Date.now() + 1000 * 60 * 15),
},
},
})
```
PR also needs review from teams who use Synthtrace to understand if the implementation is matching expectations.
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
The source code classifier we currently have was incorrectly classifying
e2e journey files as `non-package` instead of `tests or mocks` as it was
not using the name standards we used for FTR files.
We could have created a `functional-tests` package for the performance
folder (which is what we want to do in the future) but because we don't
have the feature to create ownerless packages it would not be easy to
find a given owner for that folder.
As such I'm just opting for a second solution which is applying the same
name standards to this journeys folder as we have for FTR and changing a
little the classifier to recognise it.
This should fix the problem found at
https://github.com/elastic/kibana/pull/178017.
Co-authored-by: Alex Szabo <alex.szabo@elastic.co>
## Summary
Closes elastic/kibana-operations/issues/24
This adds a second flavor of UBI image (`kibana-ubi-fips`) which has a
FIPS compliant version of OpenSSL compiled and linked to Node. Using the
label `ci:build-docker-fips` will create the image in CI and push to the
registry.
The FIPS image start the Kibana NodeJS process using the FIPS compliant
OpenSSL version. Kibana will start in this state but crash during
runtime because there are many code changes required for it to be FIPS
compliant, including `node_module` usage. I attempted numerous ways to
load other OpenSSL providers alongside the FIPS provider, but it always
led to Kibana crashing on invalid algorithm usage.
---------
Co-authored-by: Tiago Costa <tiago.costa@elastic.co>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
This PR consolidates shared ux team dev docs similar how it was done by
operations team.
There is a separate "Shared UX" toc in the nav with the team's
catalogue. Also a landing page with our catalog.
<img width="1185" alt="Screenshot 2023-12-08 at 17 01 15"
src="c8e758f0-bcaa-4c74-9187-2911b2e7a680">
## Summary
This PR removes the [duplicated RedirectAppLinks
component](https://github.com/elastic/kibana/blob/v8.10.4/src/plugins/kibana_react/public/app_links/redirect_app_link.tsx)
which has been marked as deprecated since
74a00fad20.
All references to the previous import declaration from
`@kbn/kibana-react-plugin/public` have been replaced with
`@kbn/shared-ux-link-redirect-app`, this change ensures that the current
app behaviour is preserved, and changes to match the expectation of the
new component have been applied where necessary.
Changes relating to the new `RedirectAppLinks` component;
- The component does not accept a `className` anymore as it is not a
presentational component despite it being used as one previously,
there's change to make accommodation for how it had been used.
- The component introduces a`data-test-subj` attribute with the value
`kbnRedirectAppLink` on the dom node that wraps it's children.
### 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)~
-->
- [x]
[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
<!--
~- [ ] 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—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—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>
Skipped tests are release blockers and fixing flaky tests isn't always
easy, especially if we assume that if a test passes locally, it will
also pass in CI.
We need to keep the differences between our local environments and CI in
mind and make appropriate changes that take these differences into
account but to do that, we first need to know what these differences
are!
This PR adds a high level description of a couple of key differences.
### Checklist
Delete any items that are not applicable to this PR.
- [X] 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)
- [x]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
---------
Co-authored-by: Alejandro Fernández Haro <afharo@gmail.com>
