# Backport
This will backport the following commits from `main` to `8.12`:
- [[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.12`:
- [[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>
# Backport
This will backport the following commits from `main` to `8.12`:
- [[DOCS] Backport whats new 8.12
(#175030)](https://github.com/elastic/kibana/pull/175030)
<!--- Backport version: 8.9.7 -->
### 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-01-17T15:34:23Z","message":"[DOCS]
Backport whats new 8.12 (#175030)\n\nIncorrectly labelled the original
What's New page PR for 8.12. Didn't\r\ntarget 8.12 and incorrectly used
backport:skip when the page needs to be\r\nbackported to 8.12. Backport
tool was getting stuck in cherry-picking so\r\ncopied original branch
and set this PR to target 8.12.0 to try resolve\r\nthe
issue.\r\n\r\nRelates to:
#174447","sha":"4b700f6394a11f0f70f2b3adc7c2e5214583a1ab","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","v8.12.0","v8.13.0"],"number":175030,"url":"https://github.com/elastic/kibana/pull/175030","mergeCommit":{"message":"[DOCS]
Backport whats new 8.12 (#175030)\n\nIncorrectly labelled the original
What's New page PR for 8.12. Didn't\r\ntarget 8.12 and incorrectly used
backport:skip when the page needs to be\r\nbackported to 8.12. Backport
tool was getting stuck in cherry-picking so\r\ncopied original branch
and set this PR to target 8.12.0 to try resolve\r\nthe
issue.\r\n\r\nRelates to:
#174447","sha":"4b700f6394a11f0f70f2b3adc7c2e5214583a1ab"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/175030","number":175030,"mergeCommit":{"message":"[DOCS]
Backport whats new 8.12 (#175030)\n\nIncorrectly labelled the original
What's New page PR for 8.12. Didn't\r\ntarget 8.12 and incorrectly used
backport:skip when the page needs to be\r\nbackported to 8.12. Backport
tool was getting stuck in cherry-picking so\r\ncopied original branch
and set this PR to target 8.12.0 to try resolve\r\nthe
issue.\r\n\r\nRelates to:
#174447","sha":"4b700f6394a11f0f70f2b3adc7c2e5214583a1ab"}}]}]
BACKPORT-->
# Backport
This will backport the following commits from `main` to `8.12`:
- [[DOCS] Warn against using ES|QL query rules on production
environments (#174130)](https://github.com/elastic/kibana/pull/174130)
<!--- 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-01-03T16:16:43Z","message":"[DOCS]
Warn against using ES|QL query rules on production environments
(#174130)","sha":"4ff1f5941f163142df29b1827a858996d743a431","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Alerting/RuleTypes","backport:prev-minor","v8.12.1","v8.13.0","v8.11.4"],"title":"[DOCS]
Warn against using ES|QL query rules on production
environments","number":174130,"url":"https://github.com/elastic/kibana/pull/174130","mergeCommit":{"message":"[DOCS]
Warn against using ES|QL query rules on production environments
(#174130)","sha":"4ff1f5941f163142df29b1827a858996d743a431"}},"sourceBranch":"main","suggestedTargetBranches":["8.12","8.11"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/174130","number":174130,"mergeCommit":{"message":"[DOCS]
Warn against using ES|QL query rules on production environments
(#174130)","sha":"4ff1f5941f163142df29b1827a858996d743a431"}},{"branch":"8.11","label":"v8.11.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
# Backport
This will backport the following commits from `main` to `8.12`:
- [Clarify spaces documentation
(#173866)](https://github.com/elastic/kibana/pull/173866)
<!--- Backport version: 8.9.7 -->
### 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":"2023-12-21T19:33:53Z","message":"Clarify
spaces documentation (#173866)\n\nClarifies language for securing access
to
spaces.","sha":"d76e059173f8e20047b238a47dc61c93335dbb88","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","docs","backport:all-open","v8.13.0"],"number":173866,"url":"https://github.com/elastic/kibana/pull/173866","mergeCommit":{"message":"Clarify
spaces documentation (#173866)\n\nClarifies language for securing access
to
spaces.","sha":"d76e059173f8e20047b238a47dc61c93335dbb88"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/173866","number":173866,"mergeCommit":{"message":"Clarify
spaces documentation (#173866)\n\nClarifies language for securing access
to spaces.","sha":"d76e059173f8e20047b238a47dc61c93335dbb88"}}]}]
BACKPORT-->
Co-authored-by: Larry Gregory <larry.gregory@elastic.co>
# Backport
This will backport the following commits from `main` to `8.12`:
- [[DOCS] Removes tech preview badge from log rate analysis docs
(#172935)](https://github.com/elastic/kibana/pull/172935)
<!--- Backport version: 8.9.7 -->
### 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":"2023-12-08T12:27:56Z","message":"[DOCS]
Removes tech preview badge from log rate analysis docs (#172935)\n\n##
Summary\r\n\r\nThis PR removes the `Technical Preview` badge from the
documentation\r\npage of Log Rate
Analysis.","sha":"885e5bd73bfd08ae66d330499dbfca7f0ceda643","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport",":ml","release_note:skip","docs","v8.12.0","v8.13.0"],"number":172935,"url":"https://github.com/elastic/kibana/pull/172935","mergeCommit":{"message":"[DOCS]
Removes tech preview badge from log rate analysis docs (#172935)\n\n##
Summary\r\n\r\nThis PR removes the `Technical Preview` badge from the
documentation\r\npage of Log Rate
Analysis.","sha":"885e5bd73bfd08ae66d330499dbfca7f0ceda643"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172935","number":172935,"mergeCommit":{"message":"[DOCS]
Removes tech preview badge from log rate analysis docs (#172935)\n\n##
Summary\r\n\r\nThis PR removes the `Technical Preview` badge from the
documentation\r\npage of Log Rate
Analysis.","sha":"885e5bd73bfd08ae66d330499dbfca7f0ceda643"}}]}]
BACKPORT-->
Co-authored-by: István Zoltán Szabó <szabosteve@gmail.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
Closes https://github.com/elastic/kibana/issues/163996
### To test
1) Checkout [fake tracks geo_shape
branch](https://github.com/nreese/faketracks/tree/geo_shape)
2) run npm install
3) run `node ./generate_tracks.js`
4) in kibana, create `tracks*` data view
5) create map, use "create index" and draw boundaries that intersect
tracks. See screen shot
<img width="500" alt="Screen Shot 2023-08-17 at 2 49 52 PM"
src="5f1444d7-2e12-4dd2-99c1-c730c2157e04">
6) create geo containment alert where entity index is `tracks*` and
boundaries index is `boundaries`.
7) Verify alerts get generated with entity geo_shape locations
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Relates to https://github.com/elastic/elasticsearch/pull/98330
8.10 introduces a new method to configure remote clusters (API key
based), which will live next to the existing method (certificate based).
As a result, the ES remote cluster docs will be restructured. The deep
link from "[Alerting set
up](https://www.elastic.co/guide/en/kibana/current/alerting-setup.html#alerting-ccs-setup)"
to the setting up CCS privileges section in the ES docs will break (and
would potentially bring folks to the wrong page anyway).
This PR changes the link into a link to the higher-level remote cluster
docs, from where folks can click through to the section that is relevant
to them.
resolves https://github.com/elastic/kibana/issues/162886
The default continues to be 90 days for data detetention of event log
documents, and the rollover is now controlled by DLM, as described in
[Data stream lifecycle][].
[Data stream lifecycle]:
https://www.elastic.co/guide/en/elasticsearch/reference/8.9/data-stream-lifecycle.html
## Release note
Fixes the event log data stream to use Data stream lifecycle instead of
Index Lifecycle Management. If you had previously customized the Kibana
event log ILM policy, you should now update the lifecycle of the event
log data stream itself.
## Summary
Bumps node.js to 18.17.0 (replacement for PR #144012 which was later
reverted)
As a result, these categorical additions were needed:
- `node` evocations will need the `--openssl-legacy-provider` flag,
wherever it would use certain crypto functionalities
- tests required updating of the expected HTTPS Agent call arguments,
`noDelay` seems to be a default
- `window.[NAME]` fields cannot be written directly
- some stricter typechecks
This is using our in-house built node.js 18 versions through the URLs
the proxy-cache. (built with
https://github.com/elastic/kibana-custom-nodejs-builds/pull/4)
These urls are served from a bucket, where the RHEL7/Centos7 compatible
node distributables are. (see:
https://github.com/elastic/kibana-ci-proxy-cache/pull/7)
Further todos:
- [x] check docs wording and consistency
- [ ] update the dependency report
- [x] explain custom builds in documentation
- [x] node_sass prebuilts
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Tiago Costa <tiago.costa@elastic.co>
Co-authored-by: Thomas Watson <w@tson.dk>
Closes https://github.com/elastic/kibana/issues/162215
## Summary
This PR changes the default session idle timeout for users to 3 days.
## Changes Made
- Updated default `session.idleTimeout` to `3d`.
- Updated tests to expect the new default timeout
- Updated asciidocs to match the above change
## Release notes
Change the default value of `session.idleTimeout` from 8 hours to 3
days.
