From 6e6bcc8352994a5740d89f39a1c76ebd76cb12fc Mon Sep 17 00:00:00 2001
From: Michael Hartges <33423275+michael-hartges-cg@users.noreply.github.com>
Date: Tue, 14 Apr 2026 14:16:43 +0200
Subject: [PATCH] Update deployment.adoc wrt configuring log level

providing a package name while configuring a log level is mandatory. Otherwise the application restarts w/o log level changes. Considerably also a UI bug....
---
 cloudhub-2/modules/ROOT/pages/_partials/deployment.adoc | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/cloudhub-2/modules/ROOT/pages/_partials/deployment.adoc b/cloudhub-2/modules/ROOT/pages/_partials/deployment.adoc
index 22793b3f4..e2e625385 100644
--- a/cloudhub-2/modules/ROOT/pages/_partials/deployment.adoc
+++ b/cloudhub-2/modules/ROOT/pages/_partials/deployment.adoc
@@ -81,7 +81,10 @@ If you disable logging, the *Logs* heading still appears in the Runtime Manager
 
 To configure additional log levels and categories to include in logs:
 
+Set the log level for specific a Java package class by selecting the log level, entering the `package.name`, pressing the Enter key, and click *Apply Changes*.
+
 . Click the *Monitoring* tab.
+
 . Select the log level:
 +
 ** *INFO*: Informative messages
@@ -90,11 +93,12 @@ To configure additional log levels and categories to include in logs:
 ** *ERROR*: Error messages, such as when an exception occurs
 ** *FATAL*: Fatal messages for when an application fails
 
-. Optionally, set the log level for specific a Java package class by selecting the log level, entering the `package.name`, and pressing the Enter key.
+. Enter the `package.name`, and press the Enter key.
+
 . Click *Apply Changes*.
 
 [NOTE]
-Changing the log level and clicking *Apply Changes* restarts the application.
+Changing the log level and clicking *Apply Changes* creates a new configuration and restarts the application.
 
 // end::configureLogging[]