Changing the logging levels

Use the set_logging_levels action to change the logging level for a specific deployment within an application. The application parameter determines the implementation and response. Each product or application might have its own implementation of this action.

Before you begin

To access the set_logging_levels action, you must install the command line interface (CLI) utility cpctl from the cp-serviceability pod. For more information, see Installing the cpctl utility to access support actions.

Procedure

To run the set_logging_levels action, you must set the level parameter.

The level parameter options are: trace | debug | info | warn | error | fatal
In the following example, the level parameter is set to warn.
```
cpctl diagnostics set_logging_levels --token $(oc whoami -t) --level warn
--application car
```
To get a list of parameters, run the following command:
```
cpctl diagnostics set_logging_levels --help
```
To retrieve the current logging levels in IBM Security QRadar Suite Software, use the following command to run the get_logging_levels action:
```
cpctl diagnostics get_logging_levels --token $(oc whoami -t)
```
The result is in the following format: application | deployment | level.
In the following example, the application | deployment | level parameters are platform | authsvc | fatal.
```
platform | authsvc | level=fatal
car | car | level=info
car | car-connector-config | level=info
car | car-frontend-ui | level=info
clx | clx-console | level=info
clx | clx-notifications | level=info
```
To set the logging level of a specific application, specify the application parameter in the following command:
```
cpctl diagnostics set_logging_levels --token $(oc whoami -t) --level
<level> --application <app>
```
For example, to set the logging level for the platform application to fatal, use the following command.
```
cpctl diagnostics set_logging_levels --token "$(oc whoami -t)" --level
fatal --application platform
```
To set the logging level of a specific deployment within an application, specify the deployment and application parameters in the following command:
```
cpctl diagnostics set_logging_levels --token $(oc whoami -t) --level
<level> --application <app> --deployment <dep>
```
For example, to set the logging level for the authsvc deployment in the platform application to fatal, use the following command.
```
cpctl diagnostics set_logging_levels --token "$(oc whoami -t)" --level
fatal --application platform --delpoyment authsvc
```