# Backport
This will backport the following commits from `main` to `8.x`:
- [[HTTP] Log deprecated api usages
(#207904)](https://github.com/elastic/kibana/pull/207904)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Jesus
Wahrman","email":"41008968+jesuswr@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-28T14:28:14Z","message":"[HTTP]
Log deprecated api usages (#207904)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/199616\r\n\r\nAdded a debug
logger when calling deprecated APIs. This logger is\r\ndisabled by
default, to enable it you have to
set\r\n`deprecation.enable_http_debug_logs: true`.\r\n\r\nTo test this
you can play with the config value and do a request like\r\nthis to a
deprecated
endpoint:\r\n\r\n```shell\r\n#!/bin/bash\r\nAPI_KEY=\"\"\r\ncurl -X GET
\"http://localhost:5601/api/cases/status\" -i \\\r\n-H \"Content-Type:
application/json\" \\\r\n-H \"Authorization: ApiKey $API_KEY\"\r\n```
\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\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###
Identify 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---------\r\n\r\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
florent-leborgne <florent.leborgne@elastic.co>\r\nCo-authored-by:
Jean-Louis Leysens
<jloleysens@gmail.com>","sha":"23b7f0fb33cecf080879f50a0b946d123f52f6ba","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:http","Team:Core","deprecation_warnings","v9.0.0","backport:version","v8.18.0"],"title":"[HTTP]
Log deprecated api
usages","number":207904,"url":"https://github.com/elastic/kibana/pull/207904","mergeCommit":{"message":"[HTTP]
Log deprecated api usages (#207904)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/199616\r\n\r\nAdded a debug
logger when calling deprecated APIs. This logger is\r\ndisabled by
default, to enable it you have to
set\r\n`deprecation.enable_http_debug_logs: true`.\r\n\r\nTo test this
you can play with the config value and do a request like\r\nthis to a
deprecated
endpoint:\r\n\r\n```shell\r\n#!/bin/bash\r\nAPI_KEY=\"\"\r\ncurl -X GET
\"http://localhost:5601/api/cases/status\" -i \\\r\n-H \"Content-Type:
application/json\" \\\r\n-H \"Authorization: ApiKey $API_KEY\"\r\n```
\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\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###
Identify 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---------\r\n\r\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
florent-leborgne <florent.leborgne@elastic.co>\r\nCo-authored-by:
Jean-Louis Leysens
<jloleysens@gmail.com>","sha":"23b7f0fb33cecf080879f50a0b946d123f52f6ba"}},"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/207904","number":207904,"mergeCommit":{"message":"[HTTP]
Log deprecated api usages (#207904)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/199616\r\n\r\nAdded a debug
logger when calling deprecated APIs. This logger is\r\ndisabled by
default, to enable it you have to
set\r\n`deprecation.enable_http_debug_logs: true`.\r\n\r\nTo test this
you can play with the config value and do a request like\r\nthis to a
deprecated
endpoint:\r\n\r\n```shell\r\n#!/bin/bash\r\nAPI_KEY=\"\"\r\ncurl -X GET
\"http://localhost:5601/api/cases/status\" -i \\\r\n-H \"Content-Type:
application/json\" \\\r\n-H \"Authorization: ApiKey $API_KEY\"\r\n```
\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\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###
Identify 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---------\r\n\r\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
florent-leborgne <florent.leborgne@elastic.co>\r\nCo-authored-by:
Jean-Louis Leysens
<jloleysens@gmail.com>","sha":"23b7f0fb33cecf080879f50a0b946d123f52f6ba"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Jesus Wahrman <41008968+jesuswr@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[HTTP] Add a circuit breaker for the HTTP server
(#190684)](https://github.com/elastic/kibana/pull/190684)
<!--- Backport version: 9.6.4 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)
<!--BACKPORT [{"author":{"name":"Michael
Dokolin","email":"mikhail.dokolin@elastic.co"},"sourceCommit":{"committedDate":"2025-01-27T20:29:21Z","message":"[HTTP]
Add a circuit breaker for the HTTP server (#190684)\n\nThis PR resolves
#194605 and closes#170132 and brings the following\nchanges:\n- changed
ELU metrics evaluation used for autoscaling;\n- a rate limiter to
throttle incoming requests when under a high load;\n- a configuration
option to exclude some routes from the rate
limiter.","sha":"52b7bc6f06d2651a5b8f9023e1e526147a659ab0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:http","Team:Core","v9.0.0","ci:build-serverless-image","backport:version","v8.18.0"],"title":"Add
a circuit breaker for the HTTP
server","number":190684,"url":"https://github.com/elastic/kibana/pull/190684","mergeCommit":{"message":"[HTTP]
Add a circuit breaker for the HTTP server (#190684)\n\nThis PR resolves
#194605 and closes#170132 and brings the following\nchanges:\n- changed
ELU metrics evaluation used for autoscaling;\n- a rate limiter to
throttle incoming requests when under a high load;\n- a configuration
option to exclude some routes from the rate
limiter.","sha":"52b7bc6f06d2651a5b8f9023e1e526147a659ab0"}},"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/190684","number":190684,"mergeCommit":{"message":"[HTTP]
Add a circuit breaker for the HTTP server (#190684)\n\nThis PR resolves
#194605 and closes#170132 and brings the following\nchanges:\n- changed
ELU metrics evaluation used for autoscaling;\n- a rate limiter to
throttle incoming requests when under a high load;\n- a configuration
option to exclude some routes from the rate
limiter.","sha":"52b7bc6f06d2651a5b8f9023e1e526147a659ab0"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
# Backport
This will backport the following commits from `main` to `8.x`:
- [[Docs] Add wolfi image info
(#205022)](https://github.com/elastic/kibana/pull/205022)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"wajihaparvez","email":"wajiha.parvez@elastic.co"},"sourceCommit":{"committedDate":"2025-01-09T16:10:59Z","message":"[Docs]
Add wolfi image info (#205022)\n\n## Summary\r\n\r\nAdds information
about using Wolfi container images to the Install with\r\nDocker
page.\r\n\r\nCloses:
[#594](https://github.com/elastic/platform-docs-team/issues/594)","sha":"fea598ea13d9e41ce6d2b7bcf83a1845573228a0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","v8.16.0","backport:version","v8.17.0","v8.18.0"],"title":"[Docs]
Add wolfi image
info","number":205022,"url":"https://github.com/elastic/kibana/pull/205022","mergeCommit":{"message":"[Docs]
Add wolfi image info (#205022)\n\n## Summary\r\n\r\nAdds information
about using Wolfi container images to the Install with\r\nDocker
page.\r\n\r\nCloses:
[#594](https://github.com/elastic/platform-docs-team/issues/594)","sha":"fea598ea13d9e41ce6d2b7bcf83a1845573228a0"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","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/205022","number":205022,"mergeCommit":{"message":"[Docs]
Add wolfi image info (#205022)\n\n## Summary\r\n\r\nAdds information
about using Wolfi container images to the Install with\r\nDocker
page.\r\n\r\nCloses:
[#594](https://github.com/elastic/platform-docs-team/issues/594)","sha":"fea598ea13d9e41ce6d2b7bcf83a1845573228a0"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"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: wajihaparvez <wajiha.parvez@elastic.co>
## Summary
The purpose of this PR is to clarify the 8.x documentation of
`xpack.reporting.roles.enabled`, and to focus on wording that encourages
users to set `xpack.reporting.roles.enabled: false` as a way to take
advantage of a newer access control model and grant users the least
amount of privilege they need. This adds more explain to what the
`xpack.reporting.roles.enabled` setting actually does, and explain that
these concerns are specific to 8.x.
---------
Co-authored-by: Clint Andrew Hall <clint@clintandrewhall.com>
Co-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [Add documentation for airgap install of the product documentation
(#202912)](https://github.com/elastic/kibana/pull/202912)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Pierre
Gayvallet","email":"pierre.gayvallet@elastic.co"},"sourceCommit":{"committedDate":"2024-12-06T16:55:59Z","message":"Add
documentation for airgap install of the product documentation
(#202912)\n\n## Summary\r\n\r\nPart of
https://github.com/elastic/kibana/issues/199999\r\n\r\nAdd documentation
regarding how to install the AI Assistant product\r\ndocumentation on
air-gap
environments.","sha":"e3bc923b9a414b31c944ce856e91d2664631edf2","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","docs","backport:version","Team:AI
Infra","v8.17.0","v8.18.0"],"title":"Add documentation for airgap
install of the product
documentation","number":202912,"url":"https://github.com/elastic/kibana/pull/202912","mergeCommit":{"message":"Add
documentation for airgap install of the product documentation
(#202912)\n\n## Summary\r\n\r\nPart of
https://github.com/elastic/kibana/issues/199999\r\n\r\nAdd documentation
regarding how to install the AI Assistant product\r\ndocumentation on
air-gap
environments.","sha":"e3bc923b9a414b31c944ce856e91d2664631edf2"}},"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/202912","number":202912,"mergeCommit":{"message":"Add
documentation for airgap install of the product documentation
(#202912)\n\n## Summary\r\n\r\nPart of
https://github.com/elastic/kibana/issues/199999\r\n\r\nAdd documentation
regarding how to install the AI Assistant product\r\ndocumentation on
air-gap
environments.","sha":"e3bc923b9a414b31c944ce856e91d2664631edf2"}},{"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: Pierre Gayvallet <pierre.gayvallet@elastic.co>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[Docs] Update certain references to cloud and ESS due to serverless
GA (#202184)](https://github.com/elastic/kibana/pull/202184)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"florent-leborgne","email":"florent.leborgne@elastic.co"},"sourceCommit":{"committedDate":"2024-11-28T15:53:56Z","message":"[Docs]
Update certain references to cloud and ESS due to serverless GA
(#202184)\n\nThis PR updates a few references to hosted deployments on
Elastic Cloud\r\nto avoid ambiguity with serverless in anticipation of
serverless GA.\r\n\r\nSome more similar updates will be made on other
repos to align.\r\n\r\nRel:
https://github.com/elastic/platform-docs-team/issues/485","sha":"95a7b0c044f6ef2fc360245a2085687ae3474bd8","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","backport:version","v8.17.0","v8.18.0"],"title":"[Docs]
Update certain references to cloud and ESS due to serverless
GA","number":202184,"url":"https://github.com/elastic/kibana/pull/202184","mergeCommit":{"message":"[Docs]
Update certain references to cloud and ESS due to serverless GA
(#202184)\n\nThis PR updates a few references to hosted deployments on
Elastic Cloud\r\nto avoid ambiguity with serverless in anticipation of
serverless GA.\r\n\r\nSome more similar updates will be made on other
repos to align.\r\n\r\nRel:
https://github.com/elastic/platform-docs-team/issues/485","sha":"95a7b0c044f6ef2fc360245a2085687ae3474bd8"}},"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/202184","number":202184,"mergeCommit":{"message":"[Docs]
Update certain references to cloud and ESS due to serverless GA
(#202184)\n\nThis PR updates a few references to hosted deployments on
Elastic Cloud\r\nto avoid ambiguity with serverless in anticipation of
serverless GA.\r\n\r\nSome more similar updates will be made on other
repos to align.\r\n\r\nRel:
https://github.com/elastic/platform-docs-team/issues/485","sha":"95a7b0c044f6ef2fc360245a2085687ae3474bd8"}},{"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: florent-leborgne <florent.leborgne@elastic.co>
# Backport
This will backport the following commits from `main` to `8.x`:
- [Remove mention of (secure) settings qualifier from docs
(#201900)](https://github.com/elastic/kibana/pull/201900)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Brad
White","email":"Ikuni17@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-27T21:35:39Z","message":"Remove
mention of (secure) settings qualifier from docs (#201900)\n\n##
Summary\r\n\r\nRemoves mentioning `(Secure)` settings from the keystore
docs because\r\nKibana does not have any settings which use this
qualifier.","sha":"318dacc2f54305d7b80bd636e5d04ee14026c1a6","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","v9.0.0","backport:prev-major"],"title":"Remove
mention of (secure) settings qualifier from
docs","number":201900,"url":"https://github.com/elastic/kibana/pull/201900","mergeCommit":{"message":"Remove
mention of (secure) settings qualifier from docs (#201900)\n\n##
Summary\r\n\r\nRemoves mentioning `(Secure)` settings from the keystore
docs because\r\nKibana does not have any settings which use this
qualifier.","sha":"318dacc2f54305d7b80bd636e5d04ee14026c1a6"}},"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/201900","number":201900,"mergeCommit":{"message":"Remove
mention of (secure) settings qualifier from docs (#201900)\n\n##
Summary\r\n\r\nRemoves mentioning `(Secure)` settings from the keystore
docs because\r\nKibana does not have any settings which use this
qualifier.","sha":"318dacc2f54305d7b80bd636e5d04ee14026c1a6"}}]}]
BACKPORT-->
Co-authored-by: Brad White <Ikuni17@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[doc] Allow copying as curl for saved object rollback instructions
(#200187)](https://github.com/elastic/kibana/pull/200187)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Jesus
Wahrman","email":"41008968+jesuswr@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-18T09:04:20Z","message":"[doc]
Allow copying as curl for saved object rollback instructions
(#200187)\n\n## Summary\r\n\r\nChanged the doc file so it allows to copy
as
curl.\r\n\r\n[Issue](https://github.com/elastic/kibana/issues/198490)\r\n\r\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"7cb5b4d3cc3fedfdbdb9253e0b442076158ef7a5","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","docs","v8.8.3","v8.9.3","v8.10.5","v8.11.5","v8.12.3","v8.13.5","v8.14.4","backport:version","v8.17.0","v8.16.1","v8.18.0","v8.15.5"],"title":"[doc]
Allow copying as curl for saved object rollback
instructions","number":200187,"url":"https://github.com/elastic/kibana/pull/200187","mergeCommit":{"message":"[doc]
Allow copying as curl for saved object rollback instructions
(#200187)\n\n## Summary\r\n\r\nChanged the doc file so it allows to copy
as
curl.\r\n\r\n[Issue](https://github.com/elastic/kibana/issues/198490)\r\n\r\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"7cb5b4d3cc3fedfdbdb9253e0b442076158ef7a5"}},"sourceBranch":"main","suggestedTargetBranches":["8.8","8.9","8.10","8.11","8.12","8.13","8.14","8.x","8.16","8.18","8.15"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200187","number":200187,"mergeCommit":{"message":"[doc]
Allow copying as curl for saved object rollback instructions
(#200187)\n\n## Summary\r\n\r\nChanged the doc file so it allows to copy
as
curl.\r\n\r\n[Issue](https://github.com/elastic/kibana/issues/198490)\r\n\r\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"7cb5b4d3cc3fedfdbdb9253e0b442076158ef7a5"}},{"branch":"8.8","label":"v8.8.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.9","label":"v8.9.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.10","label":"v8.10.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.11","label":"v8.11.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.12","label":"v8.12.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.13","label":"v8.13.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.14","label":"v8.14.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.15","label":"v8.15.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Jesus Wahrman <41008968+jesuswr@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[Docs] Update nav instructions and sample data installation to
accommodate for the solution views
(#199163)](https://github.com/elastic/kibana/pull/199163)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"florent-leborgne","email":"florent.leborgne@elastic.co"},"sourceCommit":{"committedDate":"2024-11-08T10:10:32Z","message":"[Docs]
Update nav instructions and sample data installation to accommodate for
the solution views (#199163)\n\nThis PR:\r\n- updates navigation
instructions to accommodate for the navigation\r\nchanges related to
solution views.\r\n- updates instructions for adding sample data to rely
on the\r\nintegrations page instead of the home page, that only exists
with the\r\nclassic solution view\r\n- updates references to the home
page to avoid confusing users using one\r\nof the new solution
views\r\n\r\nCloses:
https://github.com/elastic/platform-docs-team/issues/529\r\nCloses:
https://github.com/elastic/platform-docs-team/issues/540","sha":"8e7fb7a77e2399e3e946bbba0462517fd7dad0f7","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","v8.16.0","backport:version","v8.17.0"],"title":"[Docs]
Update nav instructions and sample data installation to accommodate for
the solution
views","number":199163,"url":"https://github.com/elastic/kibana/pull/199163","mergeCommit":{"message":"[Docs]
Update nav instructions and sample data installation to accommodate for
the solution views (#199163)\n\nThis PR:\r\n- updates navigation
instructions to accommodate for the navigation\r\nchanges related to
solution views.\r\n- updates instructions for adding sample data to rely
on the\r\nintegrations page instead of the home page, that only exists
with the\r\nclassic solution view\r\n- updates references to the home
page to avoid confusing users using one\r\nof the new solution
views\r\n\r\nCloses:
https://github.com/elastic/platform-docs-team/issues/529\r\nCloses:
https://github.com/elastic/platform-docs-team/issues/540","sha":"8e7fb7a77e2399e3e946bbba0462517fd7dad0f7"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199163","number":199163,"mergeCommit":{"message":"[Docs]
Update nav instructions and sample data installation to accommodate for
the solution views (#199163)\n\nThis PR:\r\n- updates navigation
instructions to accommodate for the navigation\r\nchanges related to
solution views.\r\n- updates instructions for adding sample data to rely
on the\r\nintegrations page instead of the home page, that only exists
with the\r\nclassic solution view\r\n- updates references to the home
page to avoid confusing users using one\r\nof the new solution
views\r\n\r\nCloses:
https://github.com/elastic/platform-docs-team/issues/529\r\nCloses:
https://github.com/elastic/platform-docs-team/issues/540","sha":"8e7fb7a77e2399e3e946bbba0462517fd7dad0f7"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[OpenAPI][DOCS] Add descriptions, examples, responses for role APIs
(#195527)](https://github.com/elastic/kibana/pull/195527)
<!--- Backport version: 8.9.8 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2024-10-25T17:13:57Z","message":"[OpenAPI][DOCS]
Add descriptions, examples, responses for role APIs
(#195527)\n\nCo-authored-by: Elena Shostak
<165678770+elena-shostak@users.noreply.github.com>","sha":"02fab7248d5b4e537030252df81bef55d04d0595","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","docs","v8.16.0","backport:version","v8.17.0"],"number":195527,"url":"https://github.com/elastic/kibana/pull/195527","mergeCommit":{"message":"[OpenAPI][DOCS]
Add descriptions, examples, responses for role APIs
(#195527)\n\nCo-authored-by: Elena Shostak
<165678770+elena-shostak@users.noreply.github.com>","sha":"02fab7248d5b4e537030252df81bef55d04d0595"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/195527","number":195527,"mergeCommit":{"message":"[OpenAPI][DOCS]
Add descriptions, examples, responses for role APIs
(#195527)\n\nCo-authored-by: Elena Shostak
<165678770+elena-shostak@users.noreply.github.com>","sha":"02fab7248d5b4e537030252df81bef55d04d0595"}},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [Updates file upload formats in Kibana guide
(#195880)](https://github.com/elastic/kibana/pull/195880)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"kosabogi","email":"105062005+kosabogi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-14T08:48:36Z","message":"Updates
file upload formats in Kibana guide (#195880)\n\n###
Overview\r\n\r\nThis PR updates the **Upload a file** section in the
**Add data** page\r\nto reflect the changes to the supported file
formats in the Data\r\nVisualizer.\r\n\r\n### Related issue:
\r\n\r\n\r\nhttps://github.com/elastic/search-docs-team/issues/189#issuecomment-2399079270\r\n\r\n###
Preview","sha":"94ee8d598fe9fdf388a49e48580c2db58e85df2b","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","v8.16.0","backport:version"],"title":"Updates
file upload formats in Kibana
guide","number":195880,"url":"https://github.com/elastic/kibana/pull/195880","mergeCommit":{"message":"Updates
file upload formats in Kibana guide (#195880)\n\n###
Overview\r\n\r\nThis PR updates the **Upload a file** section in the
**Add data** page\r\nto reflect the changes to the supported file
formats in the Data\r\nVisualizer.\r\n\r\n### Related issue:
\r\n\r\n\r\nhttps://github.com/elastic/search-docs-team/issues/189#issuecomment-2399079270\r\n\r\n###
Preview","sha":"94ee8d598fe9fdf388a49e48580c2db58e85df2b"}},"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/195880","number":195880,"mergeCommit":{"message":"Updates
file upload formats in Kibana guide (#195880)\n\n###
Overview\r\n\r\nThis PR updates the **Upload a file** section in the
**Add data** page\r\nto reflect the changes to the supported file
formats in the Data\r\nVisualizer.\r\n\r\n### Related issue:
\r\n\r\n\r\nhttps://github.com/elastic/search-docs-team/issues/189#issuecomment-2399079270\r\n\r\n###
Preview","sha":"94ee8d598fe9fdf388a49e48580c2db58e85df2b"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: kosabogi <105062005+kosabogi@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[Search] Update connectors docs URLs and doc link
(#195374)](https://github.com/elastic/kibana/pull/195374)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Liam
Thompson","email":"32779855+leemthompo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-08T12:01:34Z","message":"[Search]
Update connectors docs URLs and doc link (#195374)\n\nMissed one in
https://github.com/elastic/kibana/pull/194423","sha":"336f824122775605a98906b55e77acfcafd88691","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","Team:EnterpriseSearch","v8.16.0","backport:version"],"title":"[Search]
Update connectors docs URLs and doc
link","number":195374,"url":"https://github.com/elastic/kibana/pull/195374","mergeCommit":{"message":"[Search]
Update connectors docs URLs and doc link (#195374)\n\nMissed one in
https://github.com/elastic/kibana/pull/194423","sha":"336f824122775605a98906b55e77acfcafd88691"}},"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/195374","number":195374,"mergeCommit":{"message":"[Search]
Update connectors docs URLs and doc link (#195374)\n\nMissed one in
https://github.com/elastic/kibana/pull/194423","sha":"336f824122775605a98906b55e77acfcafd88691"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [(Docs) Add Kibana upgrade notes page
(#193268)](https://github.com/elastic/kibana/pull/193268)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"florent-leborgne","email":"florent.leborgne@elastic.co"},"sourceCommit":{"committedDate":"2024-10-07T09:51:42Z","message":"(Docs)
Add Kibana upgrade notes page (#193268)\n\n## Summary\r\n\r\nThis
PR:\r\n\r\n- adds a page that is a compiled list of all breaking changes
and\r\ndeprecations introduced since the last major version. I slightly
edited\r\nsome bits to align the wording and add version information to
each item,\r\nand took a bit of freedom (not too much!) to ignore items
that shouldn't\r\nbe identified as deprecations or breaking changes, or
to move them to\r\nthe appropriate section in this page.\r\n- adds a
link to the new page from the Upgrade Kibana page.\r\n\r\n<img
width=\"1483\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/16109072-d5c6-4eb4-8a52-ef209a07072a\">\r\n\r\n<img
width=\"810\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/939e9212-b750-4a6f-bd8f-f8df04e46d76\">\r\n\r\n\r\nI'm
wondering if we should leave this uncategorized or at least
identify\r\nwhich items are specific to a solution. It also doesn't make
much sense\r\nthat we have Obs here while we don't have Security. Let's
think about a\r\nconsistent way to do it.\r\n\r\nNote: In this PR, the
page is initially added under the Release notes\r\nsection. I'll need to
make sure that this does not interfere with the\r\nrelease notes
automation.\r\n\r\nNote 2: If we move forward with this proposal, we'll
need update the\r\nrelease notes internal docs to add the relevant
information to this page\r\nwith each minor release, or find a way to
automate.\r\n\r\nCloses:
https://github.com/elastic/kibana-team/issues/1075\r\n\r\n---------\r\n\r\nCo-authored-by:
Lisa Cawley <lcawley@elastic.co>\r\nCo-authored-by: Kaarina Tungseth
<kaarina.tungseth@elastic.co>\r\nCo-authored-by: Luke Elmers
<lukeelmers@gmail.com>","sha":"94caafd57d8fcff310ca4117cbf984bbb54658cb","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","v8.16.0","backport:version"],"title":"Add
Kibana upgrade notes
page","number":193268,"url":"https://github.com/elastic/kibana/pull/193268","mergeCommit":{"message":"(Docs)
Add Kibana upgrade notes page (#193268)\n\n## Summary\r\n\r\nThis
PR:\r\n\r\n- adds a page that is a compiled list of all breaking changes
and\r\ndeprecations introduced since the last major version. I slightly
edited\r\nsome bits to align the wording and add version information to
each item,\r\nand took a bit of freedom (not too much!) to ignore items
that shouldn't\r\nbe identified as deprecations or breaking changes, or
to move them to\r\nthe appropriate section in this page.\r\n- adds a
link to the new page from the Upgrade Kibana page.\r\n\r\n<img
width=\"1483\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/16109072-d5c6-4eb4-8a52-ef209a07072a\">\r\n\r\n<img
width=\"810\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/939e9212-b750-4a6f-bd8f-f8df04e46d76\">\r\n\r\n\r\nI'm
wondering if we should leave this uncategorized or at least
identify\r\nwhich items are specific to a solution. It also doesn't make
much sense\r\nthat we have Obs here while we don't have Security. Let's
think about a\r\nconsistent way to do it.\r\n\r\nNote: In this PR, the
page is initially added under the Release notes\r\nsection. I'll need to
make sure that this does not interfere with the\r\nrelease notes
automation.\r\n\r\nNote 2: If we move forward with this proposal, we'll
need update the\r\nrelease notes internal docs to add the relevant
information to this page\r\nwith each minor release, or find a way to
automate.\r\n\r\nCloses:
https://github.com/elastic/kibana-team/issues/1075\r\n\r\n---------\r\n\r\nCo-authored-by:
Lisa Cawley <lcawley@elastic.co>\r\nCo-authored-by: Kaarina Tungseth
<kaarina.tungseth@elastic.co>\r\nCo-authored-by: Luke Elmers
<lukeelmers@gmail.com>","sha":"94caafd57d8fcff310ca4117cbf984bbb54658cb"}},"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/193268","number":193268,"mergeCommit":{"message":"(Docs)
Add Kibana upgrade notes page (#193268)\n\n## Summary\r\n\r\nThis
PR:\r\n\r\n- adds a page that is a compiled list of all breaking changes
and\r\ndeprecations introduced since the last major version. I slightly
edited\r\nsome bits to align the wording and add version information to
each item,\r\nand took a bit of freedom (not too much!) to ignore items
that shouldn't\r\nbe identified as deprecations or breaking changes, or
to move them to\r\nthe appropriate section in this page.\r\n- adds a
link to the new page from the Upgrade Kibana page.\r\n\r\n<img
width=\"1483\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/16109072-d5c6-4eb4-8a52-ef209a07072a\">\r\n\r\n<img
width=\"810\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/939e9212-b750-4a6f-bd8f-f8df04e46d76\">\r\n\r\n\r\nI'm
wondering if we should leave this uncategorized or at least
identify\r\nwhich items are specific to a solution. It also doesn't make
much sense\r\nthat we have Obs here while we don't have Security. Let's
think about a\r\nconsistent way to do it.\r\n\r\nNote: In this PR, the
page is initially added under the Release notes\r\nsection. I'll need to
make sure that this does not interfere with the\r\nrelease notes
automation.\r\n\r\nNote 2: If we move forward with this proposal, we'll
need update the\r\nrelease notes internal docs to add the relevant
information to this page\r\nwith each minor release, or find a way to
automate.\r\n\r\nCloses:
https://github.com/elastic/kibana-team/issues/1075\r\n\r\n---------\r\n\r\nCo-authored-by:
Lisa Cawley <lcawley@elastic.co>\r\nCo-authored-by: Kaarina Tungseth
<kaarina.tungseth@elastic.co>\r\nCo-authored-by: Luke Elmers
<lukeelmers@gmail.com>","sha":"94caafd57d8fcff310ca4117cbf984bbb54658cb"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
# Backport
This will backport the following commits from `main` to `8.x`:
- [(Doc+) link video to checking health
(#193023)](https://github.com/elastic/kibana/pull/193023)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Stef
Nestor","email":"26751266+stefnestor@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-09-16T15:38:46Z","message":"(Doc+)
link video to checking health (#193023)\n\n## Summary\r\n\r\n👋 howdy
team! Ongoing improvement for common support topic, this links\r\n[this
video\r\nwalkthrough](https://www.youtube.com/watch?v=AlgGYcpGvOA&list=PL_mJOmq4zsHbQlfEMEh_30_LuV_hZp-3d&index=3)\r\non
checking Kibana health.\r\n\r\n\r\n### Checklist\r\nNA\r\n\r\n### Risk
Matrix\r\nNA\r\n\r\n### For
maintainers\r\nNA\r\n\r\n---------\r\n\r\nCo-authored-by:
florent-leborgne
<florent.leborgne@elastic.co>","sha":"6755cc180860653c9ec6f3891231a8f69f929c69","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","enhancement","release_note:skip","v9.0.0","docs","Supportability","v8.15.0","v8.16.0"],"title":"(Doc+)
link video to checking
health","number":193023,"url":"https://github.com/elastic/kibana/pull/193023","mergeCommit":{"message":"(Doc+)
link video to checking health (#193023)\n\n## Summary\r\n\r\n👋 howdy
team! Ongoing improvement for common support topic, this links\r\n[this
video\r\nwalkthrough](https://www.youtube.com/watch?v=AlgGYcpGvOA&list=PL_mJOmq4zsHbQlfEMEh_30_LuV_hZp-3d&index=3)\r\non
checking Kibana health.\r\n\r\n\r\n### Checklist\r\nNA\r\n\r\n### Risk
Matrix\r\nNA\r\n\r\n### For
maintainers\r\nNA\r\n\r\n---------\r\n\r\nCo-authored-by:
florent-leborgne
<florent.leborgne@elastic.co>","sha":"6755cc180860653c9ec6f3891231a8f69f929c69"}},"sourceBranch":"main","suggestedTargetBranches":["8.15","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/193023","number":193023,"mergeCommit":{"message":"(Doc+)
link video to checking health (#193023)\n\n## Summary\r\n\r\n👋 howdy
team! Ongoing improvement for common support topic, this links\r\n[this
video\r\nwalkthrough](https://www.youtube.com/watch?v=AlgGYcpGvOA&list=PL_mJOmq4zsHbQlfEMEh_30_LuV_hZp-3d&index=3)\r\non
checking Kibana health.\r\n\r\n\r\n### Checklist\r\nNA\r\n\r\n### Risk
Matrix\r\nNA\r\n\r\n### For
maintainers\r\nNA\r\n\r\n---------\r\n\r\nCo-authored-by:
florent-leborgne
<florent.leborgne@elastic.co>","sha":"6755cc180860653c9ec6f3891231a8f69f929c69"}},{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Stef Nestor <26751266+stefnestor@users.noreply.github.com>
## Summary
This PR echos verbiage that belongs as a footnote on the Kibana Support
Matrix web page: https://www.elastic.co/support/matrix/#matrix_os
## Checklist
- [x] Include text from the footnote of the Kibana Support Matrix
- [x] Guide users to test reporting features in a pre-production
environment
## Summary
This adds a publicBaseUrl to the Elasticsearch plugin config so users
can set a publicly accessible URL for Elasticsearch.
---------
Co-authored-by: Rudolf Meijering <skaapgif@gmail.com>
## Summary
Fix https://github.com/elastic/kibana/issues/185042
- Add a new `elasticsearch.maxResponseSize` config option
- Set this value to `100mb` on our serverless configuration file
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Part of https://github.com/elastic/kibana/issues/7104
Add support for `http2` to the Kibana server. `http2` can be enabled by
setting `server.protocol: http2` in the Kibana config file.
*Note: by default, enabling `http2` requires a valid `h2c`
configuration, meaning that it can only run over HTTPS with TLS1.2+*
```yaml
## kibana.yaml
server.protocol: http2
server.ssl.enabled: true
server.ssl.key: path/to/key
server.ssl.certificate: path/my/cerf
```
## What is this PR doing
### Add HTTP2 support for the Kibana server
#### - Plug http2 to the Kibana server
Even if HAPI was never officially updated to really support HTTP2,
node's `http`/`https`/`http2` modules are compatible enough to be able
to just instantiate an http2 server/listener and provide it to HAPI "as
a plain https listener". There were some tweaks to do (mostly silencing
a few warnings that HAPI was causing by sending http2-illegal headers
such as `Connection`), but overall, it went smoothly.
#### - Add config validation
By default, Kibana will require a valid `h2c` configuration to accept
enabling `http2`. It means that TLS must be enabled and that TLS1.2+
should at least be in the list of supported SSL protocols
(`server.ssl.supportedProtocols`). Note that default value of this
setting includes TLS1.2 and 1.3.
#### - Add escape hatch to run `h2` without `h2c`
In some situations, it may be required to enable http2 without a valid
`h2c` configuration. Kibana supports it, by setting
`server.http2.allowUnsecure` to `true`.
(*Note, however, that if http2 is enabled without TLS, ALPN protocol
negotiation won't work, meaning that most http2 agents/clients will fail
connecting unless they're explictly configured to use http2.*)
### Add documentation about this new feature
#### - Update the user-facing doc about this new `server.protocol`
setting
Update the user-facing Kibana settings documentation to include this
`http.protocol` setting (and refer to `server.http2.allowUnsecure`)
**Note: this setting, and this feature, are considered as experimental**
### Adapt our dev tooling to support running Kibana with http2 enabled
#### - Add a `--http2` flag to the dev CLI
Enabling this flag will add the proper configuration settings to run
Kibana with `http2` enabled in an (almost) valid `h2c` configutation.
*Note: when using this flag, even if listening on the same port, the
Kibana server will be accessible over https, meaning that you need to
use https in your browser to access it. Aka `http://localhost:5601`
won't work, you need to use `https://localhost:5601`. Also, we're using
the self-signed dev certificates, meaning that you must go though the
scary warning of your browser*
#### - Implement an http2-compatible base-path proxy
The current base path proxy is based on `hapi` and `hapi/h2o2`. I tried
for a bunch hours trying to hack around to make it work with http2
proxying, but ultimately gave up and implemented a new version from
scratch.
Note that with some additional efforts, this new http2 basepath proxy
could probably fully replace the existing one and be used for both http1
and http2 traffic, but it's an optimization / refactoring that did not
feel required for this PR.
### Adapt the FTR to run suites against http2
#### - Add support to run FTR test suite against an h2c-enabled Kibana
Note that with ALPN, clients using http1 should be (and are) able to
communicate with http2 Kibana, given h2c/alpn allows protocol
negitiation. So adapting our FTR tooling was not really about making it
work with http2 (which worked out of the box), but making it work with
**the self signed certifcates we use for https on dev mode**
Note that I'm not a big fan of what I had to do, however, realistically
this was the only possible approach if we want to run arbitrary test
suites with TLS/HTTP2 enabled without massively changing our FTR setup.
Operations and QA, feel free to chime in there, as this is your
territory.
#### - Change some FTR test suites to run against an HTTP2-enabled
server
I added a quick `configureHTTP2` helper function to take any "final" FTR
suite config and mutate it to enable `http2`. I then enabled it on a few
suites locally, to make sure the suites were passing correctly.
I kept two suites running with http2 enabled:
- the `console` oss functional tests
- the `home` oss functional tests
We could possibly enable it for more, but we need to figure out what
kind of strategy we want on that matter (see below)
## What is this pull request NOT doing
#### - Making sure everything works when HTTP2 is enabled
I navigated the applications quite a bit, and did not see anything
broken, however I obviously wasn't able to do a full coverage. Also, the
self-signed certificate was a huge pain to detect issues really caused
by http2 compared to issues because the local setup isn't valid `h2c`.
In theory though (famous last words) anything not doing http/1.1
specific hacks such as bfetch should work fine with http2, given that
even if using non-http2 clients, ALPN should just allow to fallback to
http/1.x (this part was tested)
#### - Enabling HTTP2 by default
PR isn't doing it for obvious reasons.
#### - Enabling HTTP2 for all FTR suites
First of all, it's not that easy, because it requires adapting various
parts of the config (and even some var env...), and we don't have any
proper way to override config "at the end". For instance, if you add the
http2 config on a top level config (e.g. the oss functional one that is
reuse by the whole world - learned the hard way), it won't work because
higher-level configs redefined (and override) the `browser` part of the
config, loosing the settings added to run the browser in insecure mode.
Secondly, I'm not sure we really need to run that many suites with http2
enabled. I learned working on that PR that we only have like one suite
where https is enabled for the Kibana server, and I feel like it could
be fine to have the same for http2. In theory it's just a protocol
change, unless parts of our apps (e.g. bfetch) are doing things that are
specific to http/1.1, switching to http2 should be an implementation
detail.
But I'd love to get @elastic/kibana-operations and @elastic/appex-qa
opinion on that one, given they have more expertise than I do on that
area.
- Running performances tests
We should absolutely run perf testing between http/1.1 over https and
http/2, to make sure that it goes into the right directly (at least in
term of user perceived speed), but I did not do it in the scope of this
PR (and @dmlemeshko is on PTO so... 😅)
## Release Note
Add support for `http2` to the Kibana server. `http2` can be enabled by
setting `server.protocol: http2` in the Kibana config file.
Note: by default, enabling `http2` requires a valid `h2c` configuration,
meaning that it can only run over HTTPS with TLS1.2+
Please refer to the Kibana config documentation for more details.
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
This adds support a password protected keystore. The UX should match
other stack products.
Closes https://github.com/elastic/kibana/issues/21756.
```
[jon@mbpkbn1]/tmp/kibana-8.15.0-SNAPSHOT% bin/kibana-keystore create --password
A Kibana keystore already exists. Overwrite? [y/N] y
Enter new password for the kibana keystore (empty for no password): ********
Created Kibana keystore in /tmp/kibana-8.15.0-SNAPSHOT/config/kibana.keystore
[jon@mbpkbn1]/tmp/kibana-8.15.0-SNAPSHOT% bin/kibana-keystore add elasticsearch.username
Enter password for the kibana keystore: ********
Enter value for elasticsearch.username: *************
[jon@mbpkbn1]/tmp/kibana-8.15.0-SNAPSHOT% bin/kibana-keystore add elasticsearch.password
Enter password for the kibana keystore: ********
Enter value for elasticsearch.password: ********
[jon@mbpkbn1]/tmp/kibana-8.15.0-SNAPSHOT% bin/kibana
...
Enter password for the kibana keystore: ********
[2024-04-30T09:47:03.560-05:00][INFO ][root] Kibana is starting
[jon@mbpkbn1]/tmp/kibana-8.15.0-SNAPSHOT% bin/kibana-keystore has-passwd
Keystore is password-protected
[jon@mbpkbn1]/tmp/kibana-8.15.0-SNAPSHOT% ./bin/kibana-keystore show elasticsearch.username
Enter password for the kibana keystore: ********
kibana_system
[jon@mbpkbn1]/tmp/kibana-8.15.0-SNAPSHOT% ./bin/kibana-keystore remove elasticsearch.username
Enter password for the kibana keystore: ********
[jon@mbpkbn1]/tmp/kibana-8.15.0-SNAPSHOT% ./bin/kibana-keystore show elasticsearch.username
Enter password for the kibana keystore: ********
ERROR: Kibana keystore doesn't have requested key.
[jon@mbpkbn1]/tmp/kibana-8.15.0-SNAPSHOT% bin/kibana-keystore passwd
Enter password for the kibana keystore: ********
Enter new password for the kibana keystore (empty for no password):
[jon@mbpkbn1]/tmp/kibana-8.15.0-SNAPSHOT% ./bin/kibana-keystore has-passwd
Error: Keystore is not password protected
[jon@mbpkbn1]/tmp/kibana-8.15.0-SNAPSHOT% ./bin/kibana
...
[2024-04-30T09:49:03.220-05:00][INFO ][root] Kibana is starting
```
## Password input
Environment variable usage is not consistent across stack products. I
implemented `KBN_KEYSTORE_PASSWORD_FILE` and `KBN_KEYSTORE_PASSWORD` to
be used to avoid prompts. @elastic/kibana-security do you have any
thoughts?
- `LOGSTASH_KEYSTORE_PASS` -
https://www.elastic.co/guide/en/logstash/current/keystore.html#keystore-password
- `KEYSTORE_PASSWORD` -
https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html#docker-keystore-bind-mount
- `ES_KEYSTORE_PASSPHRASE_FILE` -
https://www.elastic.co/guide/en/elasticsearch/reference/current/rpm.html#rpm-running-systemd
- Beats discussion, unresolved:
https://github.com/elastic/beats/issues/5737
## Release note
Adds password support to the Kibana keystore.
## Summary
Fix https://github.com/elastic/kibana/issues/100854
### Release note
The Kibana configuration file now supports assigning default value for
environment variables, using the `${VAR_ENV:defaultValue}` syntax.
Update levels ordering
## Summary
The documentation is currently reporting a misleading information
https://www.elastic.co/guide/en/kibana/current/logging-configuration.html#log-level:
<img width="546" alt="image"
src="573f82c5-51f8-4e32-a85d-6895cc1b2041">
indeed the "maximum" should be off and the "minimum" should be all,
because:
>A log record will be logged by the logger if its level **(ed: its
refers to log)** is higher than or equal to the level of its logger.
Otherwise, the log record is ignored.
There is no value smaller than all that will result in all types of logs
being outputted.
### Checklist
Delete any items that are not applicable to this PR.
### 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: Christiane (Tina) Heiligers <christiane.heiligers@elastic.co>
## Summary
1. Added `Content-Security-Policy-Report-Only` header.
2. Set `form-action` to `self` in reporting mode.
3. Created [visualization for report only CSP
violation](f6bb1300-0bb7-11ee-adde-d5df298171dd?_g=(filters:!(),refreshInterval:(pause:!t,value:60000),time:(from:'2024-04-03T22:00:00.000Z',to:'2024-04-05T21:30:00.000Z'))).
Generated a couple of reports for testing, here is [telemetry
data](https://stack-telemetry.elastic.dev/s/kibana-platform-security/app/discover#/?_g=(filters:!(),time:(from:now-24h%2Fh,to:now))&_a=(columns:!(timestamp),filters:!(('$state':(store:appState),meta:(alias:'Expected%20CSP%20violation',disabled:!f,index:'14413084-88e4-4fd4-82ba-a69c8b72ec95',negate:!t,params:!((meta:(alias:!n,disabled:!f,field:effectiveDirective,index:'14413084-88e4-4fd4-82ba-a69c8b72ec95',key:effectiveDirective,negate:!f,params:(query:script-src-elem),type:phrase),query:(match_phrase:(effectiveDirective:script-src-elem))),(meta:(alias:!n,disabled:!f,field:blockedURL,index:'14413084-88e4-4fd4-82ba-a69c8b72ec95',key:blockedURL,negate:!f,params:(query:inline),type:phrase),query:(match_phrase:(blockedURL:inline))),('$state':(store:appState),meta:(alias:!n,disabled:!f,field:lineNumber,index:'14413084-88e4-4fd4-82ba-a69c8b72ec95',key:lineNumber,negate:!f,params:(query:'286'),type:phrase),query:(match_phrase:(lineNumber:'286')))),relation:AND,type:combined),query:())),index:'14413084-88e4-4fd4-82ba-a69c8b72ec95',interval:auto,query:(language:kuery,query:'disposition%20:%20%22report%22%20'),sort:!(!(timestamp,desc)))).
4. Added `csp.report_only.form_action` field for additional csp policy
configuration.
### 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
- [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] 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)
### For maintainers
- [x] 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)
__Fixes: https://github.com/elastic/kibana/issues/179220__
## Release note
Added `Content-Security-Policy-Report-Only` header support.
Closes https://github.com/elastic/kibana/issues/164104
## Summary
**Replace "Download CSV" with "Generate CSV report" to export a CSV file
from saved search panel, deprecate "Download CSV", use a config flag for
providing the deprecated feature.**
This PR uses the `xpack.reporting.csv.enablePanelActionDownload`
kibana.yml setting, which was previously unused, for choosing behavior
of CSV export in a Dashboard saved search panel, and sets the default
value to `false`. The options allow the user to download a CSV file
without creating a report (deprecated, support will be removed in the
future) or to generate a CSV report (default).
1. Use the config as a flag to switch between implementations:
- downloading a CSV file without a generated report
- generating a CSV report
2. Updated documentation
3. Refactored / cleaned up tests
4. Increased API test coverage in Serverless
5. Better error handling in
`packages/kbn-reporting/public/reporting_api_client.ts`
### 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
- [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] 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)
## Release Note
Kibana CSV Reporting offered a feature allowing users to download a CSV
file from a saved search panel in a dashboard, without having a report
generated. This feature is now deprecated. Now, when users need to
access saved search data from a dashboard panel as CSV, a normal report
will be generated. To access the deprecated functionality, you can add
`xpack.reporting.csv.enablePanelActionDownload: true` to kibana.yml, but
this ability will be removed in a future version of Kibana.
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Fix https://github.com/elastic/kibana/issues/177138
- Add a `http.payloadTimeout` configuration option, to control the
payload timeout
- Set the default value for this option to `20s` (was `10s` previously)
## Summary
Just a small Doc Update. In the first example a POST was used and
towards a non existing handle (`_security` instead of `security`)
In the basic license example posted below this one, this is already
correct.
### Checklist
All checked - none applied.
(Though first PR in this repository, I am sorry if any mistakes were
made. If so - please point them out, will do better next time 😅 )
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
In this PR we:
* Allow using JWT credentials to grant API keys
* Extend default value of `elasticsearch.requestHeadersWhitelist` to
include both `authorization` and `es-client-authentication` to support
JWT with required client authentication _by default_. See
https://www.elastic.co/guide/en/elasticsearch/reference/8.11/jwt-auth-realm.html#jwt-realm-configuration
* Add API integration tests for both JWTs with client authentication and
without it
__NOTE:__ We're not gating this functionality with the config flag
(`xpack.security.authc.http.jwt.taggedRoutesOnly`) as we did for the
Serverless offering. It'd be a breaking change as we already implicitly
support JWT authentication without client authentication, and to be
honest, it's not really necessary anyway.
## Testing
Refer to the `Testing` section in this PR description:
https://github.com/elastic/kibana/pull/159117.
Or run already pre-configured Kibana functional test server:
1. `node scripts/functional_tests_server.js --config
x-pack/test/security_api_integration/api_keys.config.ts`
2. Create a role mapping for JWT user:
```bash
curl -X POST --location "http://localhost:9220/_security/role_mapping/jwt" \
-H "Authorization: Basic ZWxhc3RpYzpjaGFuZ2VtZQ==" \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-d "{
\"roles\": [ \"superuser\" ],
\"enabled\": true,
\"rules\": { \"all\": [{\"field\" : { \"realm.name\" : \"jwt_with_secret\" }}] }
}"
```
3. Send any Kibana API request with the following credentials:
```bash
curl -X POST --location "xxxx"
-H 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJodHRwczovL2tpYmFuYS5lbGFzdGljLmNvL2p3dC8iLCJzdWIiOiJlbGFzdGljLWFnZW50IiwiYXVkIjoiZWxhc3RpY3NlYXJjaCIsIm5hbWUiOiJFbGFzdGljIEFnZW50IiwiaWF0Ijo5NDY2ODQ4MDAsImV4cCI6NDA3MDkwODgwMH0.P7RHKZlLskS5DfVRqoVO4ivoIq9rXl2-GW6hhC9NvTSkwphYivcjpTVcyENZvxTTvJJNqcyx6rF3T-7otTTIHBOZIMhZauc5dob-sqcN_mT2htqm3BpSdlJlz60TBq6diOtlNhV212gQCEJMPZj0MNj7kZRj_GsECrTaU7FU0A3HAzkbdx15vQJMKZiFbbQCVI7-X2J0bZzQKIWfMHD-VgHFwOe6nomT-jbYIXtCBDd6fNj1zTKRl-_uzjVqNK-h8YW1h6tE4xvZmXyHQ1-9yNKZIWC7iEaPkBLaBKQulLU5MvW3AtVDUhzm6--5H1J85JH5QhRrnKYRon7ZW5q1AQ'
-H 'ES-Client-Authentication: SharedSecret my_super_secret'
....for example....
curl -X GET --location "http://localhost:5620/internal/security/me" \
-H 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJodHRwczovL2tpYmFuYS5lbGFzdGljLmNvL2p3dC8iLCJzdWIiOiJlbGFzdGljLWFnZW50IiwiYXVkIjoiZWxhc3RpY3NlYXJjaCIsIm5hbWUiOiJFbGFzdGljIEFnZW50IiwiaWF0Ijo5NDY2ODQ4MDAsImV4cCI6NDA3MDkwODgwMH0.P7RHKZlLskS5DfVRqoVO4ivoIq9rXl2-GW6hhC9NvTSkwphYivcjpTVcyENZvxTTvJJNqcyx6rF3T-7otTTIHBOZIMhZauc5dob-sqcN_mT2htqm3BpSdlJlz60TBq6diOtlNhV212gQCEJMPZj0MNj7kZRj_GsECrTaU7FU0A3HAzkbdx15vQJMKZiFbbQCVI7-X2J0bZzQKIWfMHD-VgHFwOe6nomT-jbYIXtCBDd6fNj1zTKRl-_uzjVqNK-h8YW1h6tE4xvZmXyHQ1-9yNKZIWC7iEaPkBLaBKQulLU5MvW3AtVDUhzm6--5H1J85JH5QhRrnKYRon7ZW5q1AQ' \
-H 'ES-Client-Authentication: SharedSecret my_super_secret' \
-H "Accept: application/json"
----
{
"username": "elastic-agent",
"roles": [
"superuser"
],
"full_name": null,
"email": null,
"metadata": {
"jwt_claim_sub": "elastic-agent",
"jwt_token_type": "access_token",
"jwt_claim_iss": "https://kibana.elastic.co/jwt/",
"jwt_claim_name": "Elastic Agent",
"jwt_claim_aud": [
"elasticsearch"
]
},
"enabled": true,
"authentication_realm": {
"name": "jwt_with_secret",
"type": "jwt"
},
"lookup_realm": {
"name": "jwt_with_secret",
"type": "jwt"
},
"authentication_type": "realm",
"authentication_provider": {
"type": "http",
"name": "__http__"
},
"elastic_cloud_user": false
}
```
__Fixes:__ https://github.com/elastic/kibana/issues/171522
----
Release note: The default value of the
`elasticsearch.requestHeadersWhitelist` configuration option has been
expanded to include the `es-client-authentication` HTTP header, in
addition to `authorization`.
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
The PR tackles a couple of improvements for the new `'notifications'`
plugin documentation:
- Add a link to the plugin API description in the kibana-dev-docs nav
bar.
- Convert the README to `mdx`.
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
If a CSV export is performed on an index alias, it also requires read
access to underlying indices.
This PR adds a note in Kibana docs to make users aware of this
requirement.
