From 872233d65e343d0259b0eede8de62e550188bc7e Mon Sep 17 00:00:00 2001 From: Visha Angelova Date: Thu, 7 Aug 2025 11:41:39 +0200 Subject: [PATCH 1/2] Add known issue for missing agent logging level setting --- .../release-notes/release-notes-8.19.asciidoc | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc b/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc index 930eb1e3c..e90b4cdd5 100644 --- a/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc +++ b/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc @@ -42,6 +42,21 @@ Review important information about the {fleet} and {agent} 8.19.0 release. [[known-issues-8.19.0]] === Known issues +[[known-issue-2444-8.19.0]] +.Setting the log level on individual {agents} is not possible +[%collapsible] +==== + +*Details* + + +There is a known issue where it is not possible to set the log level on individual {agents} as the *Agent logging level* setting is not available on the {agent}'s details page. + +*Impact* + + +No workaround is available at the moment, but a fix is expected to be available in a future patch release. + +==== + [[known-issue-2398-8.19.0]] .{agent} does not process Windows security events [%collapsible] From 6d07d7e4f605a99282d9b05db20acd5f637ea813 Mon Sep 17 00:00:00 2001 From: Visha Angelova Date: Thu, 7 Aug 2025 15:23:46 +0200 Subject: [PATCH 2/2] Apply review suggestion --- .../ingest-management/release-notes/release-notes-8.19.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc b/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc index e90b4cdd5..bf1b1ea6f 100644 --- a/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc +++ b/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc @@ -53,7 +53,7 @@ There is a known issue where it is not possible to set the log level on individu *Impact* + -No workaround is available at the moment, but a fix is expected to be available in a future patch release. +No workaround is available at the moment, but a fix is expected to be available in a future patch release. Note that the agent logging level can still be set on a per-policy basis in the agent policy's *Settings* tab. ====