github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 17:28:26 -04:00
Code Issues Projects Releases Packages Wiki Activity

Add Fleet audit logging memory leak to 8.8.0-8.8.1 known issues (#160566)

Browse source 
This PR adds Fleet audit logging memory leak to 8.8.0-8.8.1 known issues.  

Ref: https://github.com/elastic/kibana/pull/159807

Co-authored-by: James Rodewig <james.rodewig@elastic.co>
Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
This commit is contained in:
Pius 2023-06-29 05:51:02 -07:00 • committed by GitHub
parent a43ee939b5
commit 89b97a52ec
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 34 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

34
docs/CHANGELOG.asciidoc
View file

@ -105,6 +105,26 @@ Uptime::
Review the following information about the {kib} 8.8.1 release.
[float]
[[known-issues-8.8.1]]
=== Known issues
// tag::known-issue-159807[]
[discrete]
.Memory leak in {fleet} audit logging.
[%collapsible]
====
*Details* +
{fleet} introduced audit logging for various CRUD (create, read, update, and delete) operations in version 8.8.0.
While audit logging is not enabled by default, we have identified an off-heap memory leak in the implementation of {fleet} audit logging that can result in poor {kib} performance, and in some cases {kib} instances being terminated by the OS kernel's oom-killer. This memory leak can occur even when {kib} audit logging is not explicitly enabled (regardless of whether `xpack.security.audit.enabled` is set in the `kibana.yml` settings file).
*Impact* +
The version 8.8.2 release includes in {kibana-pull}159807[a fix] for this problem. If you are using {fleet} integrations
and {kib} audit logging in version 8.8.0 or 8.8.1, you should upgrade to 8.8.2 or above to obtain the fix.
====
// end::known-issue-159807[]
[float]
[[breaking-changes-8.8.1]]
=== Breaking changes
@ -196,6 +216,20 @@ The 8.8.1 release includes in {kibana-pull}158940[a fix] for this problem. Custo
====
// end::known-issue-158940[]
// tag::known-issue-159807[]
[discrete]
.Memory leak in {fleet} audit logging.
[%collapsible]
====
*Details* +
{fleet} introduced audit logging for various CRUD (create, read, update, and delete) operations in version 8.8.0.
While audit logging is not enabled by default, we have identified an off-heap memory leak in the implementation of {fleet} audit logging that can result in poor {kib} performance, and in some cases {kib} instances being terminated by the OS kernel's oom-killer. This memory leak can occur even when {kib} audit logging is not explicitly enabled (regardless of whether `xpack.security.audit.enabled` is set in the `kibana.yml` settings file).
*Impact* +
The version 8.8.2 release includes in {kibana-pull}159807[a fix] for this problem. If you are using {fleet} integrations
and {kib} audit logging in version 8.8.0 or 8.8.1, you should upgrade to 8.8.2 or above to obtain the fix.
====
// end::known-issue-159807[]
// tag::known-issue-155203[]
[discrete]
.Monitors in Synthetics may stop running