Changing log level for IBM Storage Scale DAS components
Change the log level collection for IBM Storage Scale DAS components.
You can change log levels for the following IBM Storage Scale DAS components:
NooBaacomponent logs- IBM Storage Scale DAS operator and IBM Storage Scale DAS endpoint logs
- Change the verbosity of openshift-storage namespace for noobaa component logs
- For the
openshift-storagenamespace, the following log levels are available.default_levelallNote: Thedefault_levelis0andallis5.
openshift-storagenamespace is set todefault_level. To increase the verbosity of logs for theNooBaacomponent, change the log level to a higher value (0 is set as default):Note: The noobaa command is available from the RedHat ODF package as a separate rpm.For example:noobaa system set-debug-level 3 INFO[0000] ✅ Exists: NooBaa "noobaa" INFO[0000] ✅ Exists: Service "noobaa-mgmt" INFO[0000] ✅ Exists: Secret "noobaa-operator" INFO[0000] ✅ Exists: Secret "noobaa-admin" INFO[0000] ✈️ RPC: redirector.publish_to_cluster() Request: {Target: MethodAPI:debug_api MethodName:set_debug_level RequestParams:{Module:core Level:3}} WARN[0000] RPC: GetConnection creating connection to wss://localhost:43503/rpc/ 0xc000522d20 INFO[0000] RPC: Connecting websocket (0xc000522d20) &{RPC:0xc00009d4a0 Address:wss://localhost:43503/rpc/ State:init WS:<nil> PendingRequests:map[] NextRequestID:0 Lock:{state:1 sema:0} ReconnectDelay:0s cancelPings:<nil>} INFO[0000] RPC: Connected websocket (0xc000522d20) &{RPC:0xc00009d4a0 Address:wss://localhost:43503/rpc/ State:init WS:<nil> PendingRequests:map[] NextRequestID:0 Lock:{state:1 sema:0} ReconnectDelay:0s cancelPings:<nil>} INFO[0000] ✅ RPC: redirector.publish_to_cluster() Response OK: took 6.0ms Debug level was set to 3 successfully Debug level is not persistent and is only effective for the currently running core and endpoints pods - Change the log level for das-operator and das-endpoint pods
- For the
das-operatoranddas-endpointpods, the following log levels are available.INFODEBUGERRORWARN
das-operatoranddas-endpointpods as follows:- Change the context to the
ibm-spectrum-scale-dasnamespace.oc project ibm-spectrum-scale-das - Change the
LOG_LEVELenvironment variable under thespecsection fordas-operator-controller-managerspec.oc edit deployment ibm-spectrum-scale-das-controller-managerFor example,spec: ... ... spec: containers: ... ... env: - name: LOG_LEVEL value: DEBUG
Once the log level is changed for the IBM Storage Scale DAS operator and IBM Storage Scale DAS endpoint, it automatically gets applied to the
das-endpointpods, when thedas-operatorreconciles thedas-endpointpods with the changed log level.