# Backport
This will backport the following commits from `main` to `8.13`:
- [[DOCS] Adjusts log rate analysis docs
(#185008)](https://github.com/elastic/kibana/pull/185008)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"István Zoltán
Szabó","email":"szabosteve@gmail.com"},"sourceCommit":{"committedDate":"2024-06-12T09:19:14Z","message":"[DOCS]
Adjusts log rate analysis docs (#185008)\n\n## Summary\r\n\r\nThis PR
slightly adjusts the Log rate analysis docs to:\r\n\r\n* separate the
conceptual info more distinctively from the Kibana\r\nrelevant
parts,\r\n* highlight that the component is embedded in other
UIs.","sha":"3ae7ba5ad9c82c51d38448fe07d6dba6c6b2627c","branchLabelMapping":{"^v8.15.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","v8.13.0","v8.14.0","v8.15.0"],"title":"[DOCS]
Adjusts log rate analysis
docs","number":185008,"url":"https://github.com/elastic/kibana/pull/185008","mergeCommit":{"message":"[DOCS]
Adjusts log rate analysis docs (#185008)\n\n## Summary\r\n\r\nThis PR
slightly adjusts the Log rate analysis docs to:\r\n\r\n* separate the
conceptual info more distinctively from the Kibana\r\nrelevant
parts,\r\n* highlight that the component is embedded in other
UIs.","sha":"3ae7ba5ad9c82c51d38448fe07d6dba6c6b2627c"}},"sourceBranch":"main","suggestedTargetBranches":["8.13","8.14"],"targetPullRequestStates":[{"branch":"8.13","label":"v8.13.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.14","label":"v8.14.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.15.0","branchLabelMappingKey":"^v8.15.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/185008","number":185008,"mergeCommit":{"message":"[DOCS]
Adjusts log rate analysis docs (#185008)\n\n## Summary\r\n\r\nThis PR
slightly adjusts the Log rate analysis docs to:\r\n\r\n* separate the
conceptual info more distinctively from the Kibana\r\nrelevant
parts,\r\n* highlight that the component is embedded in other
UIs.","sha":"3ae7ba5ad9c82c51d38448fe07d6dba6c6b2627c"}}]}] BACKPORT-->
Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com>
# Backport
This will backport the following commits from `main` to `8.13`:
- [describe the values in the CCR metrics table
(#184545)](https://github.com/elastic/kibana/pull/184545)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"shainaraskas","email":"58563081+shainaraskas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-06-03T14:46:40Z","message":"describe
the values in the CCR metrics table
(#184545)","sha":"5a3251af2fb1cafc36c002009d0296f8b58f057a","branchLabelMapping":{"^v8.15.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","Feature:CCR
and Remote
Clusters","release_note:skip","docs","v8.13.0","v8.14.0","v8.15.0"],"title":"describe
the values in the CCR metrics
table","number":184545,"url":"https://github.com/elastic/kibana/pull/184545","mergeCommit":{"message":"describe
the values in the CCR metrics table
(#184545)","sha":"5a3251af2fb1cafc36c002009d0296f8b58f057a"}},"sourceBranch":"main","suggestedTargetBranches":["8.13","8.14"],"targetPullRequestStates":[{"branch":"8.13","label":"v8.13.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.14","label":"v8.14.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.15.0","branchLabelMappingKey":"^v8.15.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/184545","number":184545,"mergeCommit":{"message":"describe
the values in the CCR metrics table
(#184545)","sha":"5a3251af2fb1cafc36c002009d0296f8b58f057a"}}]}]
BACKPORT-->
Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.13`:
- [Adding the whats new in 8.13 page
(#179097)](https://github.com/elastic/kibana/pull/179097)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"amyjtechwriter","email":"61687663+amyjtechwriter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-03-25T19:19:54Z","message":"Adding
the whats new in 8.13 page (#179097)\n\nThis PR adds details about whats
new to the 8.13 release on the [whats\r\nnew
page](https://www.elastic.co/guide/en/kibana/8.10/whats-new.html).\r\n\r\nCloses:
[#179049](https://github.com/elastic/kibana/issues/179049)\r\n\r\n---------\r\n\r\nCo-authored-by:
lcawl
<lcawley@elastic.co>","sha":"0a949de7c81c0ed519e292a956d32f8777ef9bbf","branchLabelMapping":{"^v8.14.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","v8.13.0","v8.14.0"],"title":"Adding
the whats new in 8.13
page","number":179097,"url":"https://github.com/elastic/kibana/pull/179097","mergeCommit":{"message":"Adding
the whats new in 8.13 page (#179097)\n\nThis PR adds details about whats
new to the 8.13 release on the [whats\r\nnew
page](https://www.elastic.co/guide/en/kibana/8.10/whats-new.html).\r\n\r\nCloses:
[#179049](https://github.com/elastic/kibana/issues/179049)\r\n\r\n---------\r\n\r\nCo-authored-by:
lcawl
<lcawley@elastic.co>","sha":"0a949de7c81c0ed519e292a956d32f8777ef9bbf"}},"sourceBranch":"main","suggestedTargetBranches":["8.13"],"targetPullRequestStates":[{"branch":"8.13","label":"v8.13.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.14.0","branchLabelMappingKey":"^v8.14.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/179097","number":179097,"mergeCommit":{"message":"Adding
the whats new in 8.13 page (#179097)\n\nThis PR adds details about whats
new to the 8.13 release on the [whats\r\nnew
page](https://www.elastic.co/guide/en/kibana/8.10/whats-new.html).\r\n\r\nCloses:
[#179049](https://github.com/elastic/kibana/issues/179049)\r\n\r\n---------\r\n\r\nCo-authored-by:
lcawl
<lcawley@elastic.co>","sha":"0a949de7c81c0ed519e292a956d32f8777ef9bbf"}}]}]
BACKPORT-->
Co-authored-by: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.13`:
- [[DOCS] Discover troubleshooting blog link
(#179109)](https://github.com/elastic/kibana/pull/179109)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"amyjtechwriter","email":"61687663+amyjtechwriter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-03-21T17:40:52Z","message":"[DOCS]
Discover troubleshooting blog link (#179109)\n\nRequest to link from
Discover page to a blog [troubleshooting guide
for\r\nDiscover](https://www.elastic.co/blog/troubleshooting-guide-common-issues-kibana-discover-load).\r\nI've
put it under a Troubleshooting heading on the [Discover
index\r\npage](https://www.elastic.co/guide/en/kibana/current/discover.html),
but\r\nif you think it would be better included in the What's next?
section\r\njust let me know and I'll move it.\r\n\r\n<img width=\"1366\"
alt=\"Screenshot 2024-03-20 at 20 18
45\"\r\nsrc=\"c0a9d410-c0e2-4350-985f-07d432dbcdf0\">\r\n\r\nRelates
to:#178046","sha":"4d51cad82fdbbe5b958c51d12d9070db8a023a1b","branchLabelMapping":{"^v8.14.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","v8.12.0","v8.13.0","v8.14.0"],"title":"[DOCS]
Discover troubleshooting blog
link","number":179109,"url":"https://github.com/elastic/kibana/pull/179109","mergeCommit":{"message":"[DOCS]
Discover troubleshooting blog link (#179109)\n\nRequest to link from
Discover page to a blog [troubleshooting guide
for\r\nDiscover](https://www.elastic.co/blog/troubleshooting-guide-common-issues-kibana-discover-load).\r\nI've
put it under a Troubleshooting heading on the [Discover
index\r\npage](https://www.elastic.co/guide/en/kibana/current/discover.html),
but\r\nif you think it would be better included in the What's next?
section\r\njust let me know and I'll move it.\r\n\r\n<img width=\"1366\"
alt=\"Screenshot 2024-03-20 at 20 18
45\"\r\nsrc=\"c0a9d410-c0e2-4350-985f-07d432dbcdf0\">\r\n\r\nRelates
to:#178046","sha":"4d51cad82fdbbe5b958c51d12d9070db8a023a1b"}},"sourceBranch":"main","suggestedTargetBranches":["8.12","8.13"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.13","label":"v8.13.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.14.0","branchLabelMappingKey":"^v8.14.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/179109","number":179109,"mergeCommit":{"message":"[DOCS]
Discover troubleshooting blog link (#179109)\n\nRequest to link from
Discover page to a blog [troubleshooting guide
for\r\nDiscover](https://www.elastic.co/blog/troubleshooting-guide-common-issues-kibana-discover-load).\r\nI've
put it under a Troubleshooting heading on the [Discover
index\r\npage](https://www.elastic.co/guide/en/kibana/current/discover.html),
but\r\nif you think it would be better included in the What's next?
section\r\njust let me know and I'll move it.\r\n\r\n<img width=\"1366\"
alt=\"Screenshot 2024-03-20 at 20 18
45\"\r\nsrc=\"c0a9d410-c0e2-4350-985f-07d432dbcdf0\">\r\n\r\nRelates
to:#178046","sha":"4d51cad82fdbbe5b958c51d12d9070db8a023a1b"}}]}]
BACKPORT-->
Co-authored-by: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.13`:
- [[DOCS] Clarify that all rules support alert summaries
(#177755)](https://github.com/elastic/kibana/pull/177755)
<!--- Backport version: 9.4.3 -->
### 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-03-12T21:20:14Z","message":"[DOCS]
Clarify that all rules support alert summaries
(#177755)","sha":"ea99e780e7fbab19a0b11bd7eeb8c2f3428513ad","branchLabelMapping":{"^v8.14.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","docs","v8.13.0","v8.14.0"],"title":"[DOCS]
Clarify that all rules support alert
summaries","number":177755,"url":"https://github.com/elastic/kibana/pull/177755","mergeCommit":{"message":"[DOCS]
Clarify that all rules support alert summaries
(#177755)","sha":"ea99e780e7fbab19a0b11bd7eeb8c2f3428513ad"}},"sourceBranch":"main","suggestedTargetBranches":["8.13"],"targetPullRequestStates":[{"branch":"8.13","label":"v8.13.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.14.0","branchLabelMappingKey":"^v8.14.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/177755","number":177755,"mergeCommit":{"message":"[DOCS]
Clarify that all rules support alert summaries
(#177755)","sha":"ea99e780e7fbab19a0b11bd7eeb8c2f3428513ad"}}]}]
BACKPORT-->
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
# Backport
This will backport the following commits from `main` to `8.13`:
- [[DOCS] Replace table of links with single link to Obs alerting docs
(#177525)](https://github.com/elastic/kibana/pull/177525)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"DeDe
Morton","email":"dede.morton@elastic.co"},"sourceCommit":{"committedDate":"2024-03-11T18:34:31Z","message":"[DOCS]
Replace table of links with single link to Obs alerting docs
(#177525)\n\n## Summary\r\n\r\nReplaces the categorized table of links
with a single link to the\r\nobservability alerting docs because this
table is likely to get stale\r\nover time (in fact, it already is
stale).\r\n\r\nThe change looks like this when rendered in
HTML:\r\n\r\n\r\n\r\n\r\n\r\nNotes/open
issues:\r\n- [x] The [main
alerting\r\npage](https://www.elastic.co/guide/en/kibana/master/alerting-getting-started.html)\r\nfor
Kibana now has links to related alerting documentation, but is
it\r\nclear that those links point to docs that describe how to manage
alerts\r\nfrom those apps? The link text seems maybe not descriptive
enough and\r\nmight be causing confusion. _NO CHANGE REQUIRED: I'm going
to leave this\r\nas-is because I think the feedback we received
initially about the lack\r\nof links was before the links were
added._\r\n- [x] In the intro, I feel a thought might be missing from
this\r\nstatement: \"For information on creating security rules, refer
to Create\r\na detection rule.\" Should this instead say something like:
\"Security\r\nrules must be defined in the Security app. For more
information, refer\r\nto the security docs about creating a detection
rule.\" _RESOLVED_\r\n- [x] I think the descriptions about each app's
alerting capabilities\r\nshould be more consistent, but I don't want to
rewrite other folk's\r\nsections. So I have aligned my description with
the security section,\r\nfor better or worse. It's hard to make this
info consistent when each\r\nsolution/app is doing its own thing with
alerting. _DEFERRED: We will\r\nfix inconsistencies later._\r\n- [x] Is
it correct to say \"create alerts\" rather than something
like\r\n\"trigger alerts\" or \"generate alerts\"? _RESOLVED: Will keep
as \"create\"\r\nfor now since the UI is not using
\"trigger.\"_\r\n\r\n### Checklist\r\n\r\nn/a\r\n\r\ncc @lcawl Can you
help me sort through my list of open issues?\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"881980aea01e15ff20f8fbbe01912ae8d547d075","branchLabelMapping":{"^v8.14.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v8.14.0","v8.12.3"],"title":"[DOCS]
Replace table of links with single link to Obs alerting
docs","number":177525,"url":"https://github.com/elastic/kibana/pull/177525","mergeCommit":{"message":"[DOCS]
Replace table of links with single link to Obs alerting docs
(#177525)\n\n## Summary\r\n\r\nReplaces the categorized table of links
with a single link to the\r\nobservability alerting docs because this
table is likely to get stale\r\nover time (in fact, it already is
stale).\r\n\r\nThe change looks like this when rendered in
HTML:\r\n\r\n\r\n\r\n\r\n\r\nNotes/open
issues:\r\n- [x] The [main
alerting\r\npage](https://www.elastic.co/guide/en/kibana/master/alerting-getting-started.html)\r\nfor
Kibana now has links to related alerting documentation, but is
it\r\nclear that those links point to docs that describe how to manage
alerts\r\nfrom those apps? The link text seems maybe not descriptive
enough and\r\nmight be causing confusion. _NO CHANGE REQUIRED: I'm going
to leave this\r\nas-is because I think the feedback we received
initially about the lack\r\nof links was before the links were
added._\r\n- [x] In the intro, I feel a thought might be missing from
this\r\nstatement: \"For information on creating security rules, refer
to Create\r\na detection rule.\" Should this instead say something like:
\"Security\r\nrules must be defined in the Security app. For more
information, refer\r\nto the security docs about creating a detection
rule.\" _RESOLVED_\r\n- [x] I think the descriptions about each app's
alerting capabilities\r\nshould be more consistent, but I don't want to
rewrite other folk's\r\nsections. So I have aligned my description with
the security section,\r\nfor better or worse. It's hard to make this
info consistent when each\r\nsolution/app is doing its own thing with
alerting. _DEFERRED: We will\r\nfix inconsistencies later._\r\n- [x] Is
it correct to say \"create alerts\" rather than something
like\r\n\"trigger alerts\" or \"generate alerts\"? _RESOLVED: Will keep
as \"create\"\r\nfor now since the UI is not using
\"trigger.\"_\r\n\r\n### Checklist\r\n\r\nn/a\r\n\r\ncc @lcawl Can you
help me sort through my list of open issues?\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"881980aea01e15ff20f8fbbe01912ae8d547d075"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.14.0","branchLabelMappingKey":"^v8.14.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/177525","number":177525,"mergeCommit":{"message":"[DOCS]
Replace table of links with single link to Obs alerting docs
(#177525)\n\n## Summary\r\n\r\nReplaces the categorized table of links
with a single link to the\r\nobservability alerting docs because this
table is likely to get stale\r\nover time (in fact, it already is
stale).\r\n\r\nThe change looks like this when rendered in
HTML:\r\n\r\n\r\n\r\n\r\n\r\nNotes/open
issues:\r\n- [x] The [main
alerting\r\npage](https://www.elastic.co/guide/en/kibana/master/alerting-getting-started.html)\r\nfor
Kibana now has links to related alerting documentation, but is
it\r\nclear that those links point to docs that describe how to manage
alerts\r\nfrom those apps? The link text seems maybe not descriptive
enough and\r\nmight be causing confusion. _NO CHANGE REQUIRED: I'm going
to leave this\r\nas-is because I think the feedback we received
initially about the lack\r\nof links was before the links were
added._\r\n- [x] In the intro, I feel a thought might be missing from
this\r\nstatement: \"For information on creating security rules, refer
to Create\r\na detection rule.\" Should this instead say something like:
\"Security\r\nrules must be defined in the Security app. For more
information, refer\r\nto the security docs about creating a detection
rule.\" _RESOLVED_\r\n- [x] I think the descriptions about each app's
alerting capabilities\r\nshould be more consistent, but I don't want to
rewrite other folk's\r\nsections. So I have aligned my description with
the security section,\r\nfor better or worse. It's hard to make this
info consistent when each\r\nsolution/app is doing its own thing with
alerting. _DEFERRED: We will\r\nfix inconsistencies later._\r\n- [x] Is
it correct to say \"create alerts\" rather than something
like\r\n\"trigger alerts\" or \"generate alerts\"? _RESOLVED: Will keep
as \"create\"\r\nfor now since the UI is not using
\"trigger.\"_\r\n\r\n### Checklist\r\n\r\nn/a\r\n\r\ncc @lcawl Can you
help me sort through my list of open issues?\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"881980aea01e15ff20f8fbbe01912ae8d547d075"}},{"branch":"8.12","label":"v8.12.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: DeDe Morton <dede.morton@elastic.co>
## Summary
Resolves https://github.com/elastic/kibana/issues/166095.
This updates the API Key management screen to reflect the copy
adjustments described in #166095:
1. Change `Cross-Cluster` to `Cross-cluster`, unless it is mid-sentence
in which case `cross-cluster` should be used.
2. Updated ownership & expiry warnings to use the active voice.
3. Renamed `Personal` API Keys to `User` API Keys.
View docs changes here:
https://kibana_bk_175809.docs-preview.app.elstc.co/diff
Incorrectly labelled the original What's New page PR for 8.12. Didn't
target 8.12 and incorrectly used backport:skip when the page needs to be
backported to 8.12. Backport tool was getting stuck in cherry-picking so
copied original branch and set this PR to target 8.12.0 to try resolve
the issue.
Relates to: #174447
## Summary
Closes#156121
This PR is for Issue #156121 and adds the ability to perform [IP
Prefix](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-ipprefix-aggregation.html)
aggregation-based visualizations within the Kibana UI. Previously this
aggregation could only be done in DevTools as a manual query to
Elasticsearch and not visualized.
### Various Notes
* The following two folders & their subfolders had files modified for
this
* src/plugins/vis_default_editor/public/components
* src/plugins/data/common/search/aggs
* I spent a fair amount of time debating & attempting to build the
PrefixLength Input boxes and their interplay with the is_ipv6 toggle
button. Originally I tried having only 1 PrefixLength button that the
toggle switch would modify the max value / validate the contents of.
* In the end, it seemed much cleaner & straightforward to have two
separate input boxes (both prefix_length.tsx components) and just create
them with different options. This means that when a user toggles the
switch back and forth, they would be seeing/editing two different Prefix
Length boxes depending on which way the switch is.
* To make it a little more clear they are different boxes, I put "IPv4"
and "IPv6" in the label name for these boxes. Additionally, I think it
is helpful this way if you are potentially swapping back and forth
between v4 and v6 visualizations.
* There is 4 new unit tests, all related to input options, added in the
ip_prefix_fn.test.ts file
* Note - here is a test CSV file of IPv4 addresses one could import to
test locally and see this addition.
[alphadataset.csv](13691358/alphadataset.csv)
* Configure the Override settings in this way if uploading it to
Kibana/Elastic
*
### 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] [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] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [x] 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))
- [x] 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))
- [x] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)
### Risk Matrix
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 |
|---------------------------|-------------|----------|-------------------------|
### 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: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
This PR adds details about whats new to the 8.11 release on the [whats
new page](https://www.elastic.co/guide/en/kibana/8.10/whats-new.html).
---------
Co-authored-by: James Rodewig <james.rodewig@elastic.co>
Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>
Co-authored-by: Brandon Morelli <bmorelli25@gmail.com>
## Summary
Two pages about ES|QL added to the Kibana guide. One page (titled ES|QL)
under the 'Kibana concepts' heading, which is an overview page. One page
added to the 'Discover' section (titled Try ES|QL) which is a short
tutorial.
Relates to:
[#244](https://github.com/elastic/platform-docs-team/issues/244)
---------
Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>
Fixes https://github.com/elastic/kibana/issues/163959
While digging into the original issue, it was determined that the
existing components were unsalvageable. Fixing all of the issues would
have required more work than just starting over. Problems with original
components include:
1) updating rule state on component load. This is the cause of the
reported bug.
2) lack of loading state when performing async tasks, like loading data
views.
3) not displaying validation errors. When users clicked "save" with
missing configuration, no UI notifications were displayed
4) Heavy use of EuiExpression made it impossible to view all
configuration in a single time
Now, geo containment form:
1) Only updates rule state when users interact with inputs.
2) Displays loading state when performing async tasks, like loading data
views.
3) Displays validation errors
4) Has a simpler UI that allows users to see all configuration
information at the same time.
<img width="300" alt="Screen Shot 2023-08-30 at 5 34 00 PM"
src="65abfa5d-6c8e-45a9-b69f-cc07f5be7184">
<img width="300" alt="Screen Shot 2023-08-30 at 5 34 48 PM"
src="63b5af12-7104-43ae-a836-0236cf9d1e98">
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Problem: The [Configure security in Kibana](https://www.elastic.co/guide/en/kibana/current/using-kibana-with-security.html) docs page only covers the `xpack.security.encryptionKey` setting for session encryption. Users may not know that encryption for Kibana's reporting and saved objects features also require encryption keys.
Solution: Add a cross-link to the respective encryption key settings for reporting and saved objects
