This is an automated email from the ASF dual-hosted git repository.

manirajv06 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/yunikorn-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 40f1387907 [YUNIKORN-3314] Update logging subsystem values (#563)
40f1387907 is described below

commit 40f1387907f60e650ac09b28ee00dd59580080e2
Author: Wilfred Spiegelenburg <[email protected]>
AuthorDate: Tue Jun 30 20:27:09 2026 +0530

    [YUNIKORN-3314] Update logging subsystem values (#563)
    
    Update the supported log subsystem values in the documentation.
    Added:
    * deprecation (now supported in K8shim also)
    * core.diagnostics (1.5 ?)
    * core.scheduler.nodesusage (1.5)
    * core.scheduler.preemption.quotachange (1.8)
    * core.scheduler.preemption.requirednode (1.8)
    * shim.placeholder.config (1.9)
    
    Removed:
    * shim.appmgmt (1.6 ?)
    * shim.appmgmt.general (1.6 ?)
    * shim.appmgmt.sparkoperator (1.7)
    * shim.scheduler.plugin (1.9)
    
    Closes: #563
    
    Signed-off-by: Manikandan R <[email protected]>
---
 docs/user_guide/service_config.md | 28 ++++++++++++++++++++--------
 1 file changed, 20 insertions(+), 8 deletions(-)

diff --git a/docs/user_guide/service_config.md 
b/docs/user_guide/service_config.md
index 453ec222ff..dad329b375 100644
--- a/docs/user_guide/service_config.md
+++ b/docs/user_guide/service_config.md
@@ -827,7 +827,7 @@ Sets the verbosity that YuniKorn subsystem will log at.
 Yunikorn allows fine-grained logging configuration in a hierarchical manner. 
For example,
 setting an entry for `log.core.level` will configure all loggers that start 
with `core.`
 (including `core.scheduler`, etc.) unless a more specific configuration is 
present.
-Each subsystem[^1] has its log level.
+Each subsystem allows configuring a separate log level. The list of subsystems 
is defined [here](#log-subsystem-values) 
 
 A change to this setting will be picked up without a restart of YuniKorn. The 
available
 values can be numeric or textual:
@@ -846,10 +846,11 @@ Example:
 
 The `log.level` is the default log level for all loggers.
 
+Example configuration with a log level set to INFO except for the admission 
controller (DEBUG), and the core configuration code (WARN). 
 ```yaml
 log.level: "INFO"
 log.admission.level: "DEBUG"
-log.core.config.level: "INFO"
+log.core.config.level: "WARN"
 ```
 
 ### Kubernetes settings
@@ -1145,14 +1146,19 @@ Example:
 admissionController.filtering.defaultQueue: ""
 ```
 
-[^1]: Available log subsystem values:
+### Log subsystem values
+
+#### Admission controller
     - admission
     - admission.client
     - admission.conf
     - admission.utils
     - admission.webhook
+
+#### Scheduler core
     - core
     - core.config
+    - core.diagnostics
     - core.entrypoint
     - core.events
     - core.metrics
@@ -1169,19 +1175,20 @@ admissionController.filtering.defaultQueue: ""
     - core.scheduler.fsm
     - core.scheduler.health
     - core.scheduler.node
+    - core.scheduler.nodesusage
     - core.scheduler.partition
     - core.scheduler.preemption
+    - core.scheduler.preemption.quotachange
+    - core.scheduler.preemption.requirednode
     - core.scheduler.queue
     - core.scheduler.reservation
     - core.scheduler.ugm
     - core.security
     - core.utils
-    - deprecation
+
+#### Kubernetes shim
     - kubernetes
     - shim
-    - shim.appmgmt
-    - shim.appmgmt.general
-    - shim.appmgmt.sparkoperator
     - shim.cache.application
     - shim.cache.external
     - shim.cache.node
@@ -1193,9 +1200,14 @@ admissionController.filtering.defaultQueue: ""
     - shim.dispatcher
     - shim.framework
     - shim.fsm
+    - shim.placeholder.config
     - shim.predicates
     - shim.resources
     - shim.rmcallback
     - shim.scheduler
-    - shim.scheduler.plugin
     - shim.utils
+
+#### Special purpose logger
+Supported by the admission controller, core and kubernetes shim
+
+    - deprecation


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to