Enabling debug level logging for a QRadar Connected Assets and Risk connector

Enable debug level logging if you encounter an error when you import assets from an IBM® QRadar data source or if you need more detailed information about how the connector is operating. To enable debug level logging for the QRadar Connected Assets and Risk connector, you can use Red Hat® OpenShift® Console, kubectl, or oc.

Before you begin

Configure a QRadar Universal Data Insights data source connection and a QRadar Connected Assets and Risk data source connection. For more information, see Connecting to an IBM Security QRadar data source and Connecting to a QRadar asset data source.

About this task

Debug level logging occurs only during a connector import from a QRadar data source, when the connector's cron job creates a connector pod.

To enable debug level logging by using Red Hat OpenShift Console, you must have a Red Hat OpenShift login. To enable debug level logging by using kubectl or oc, you must have an oc login.

Procedure

To enable debug level logging by using Red Hat OpenShift Console, complete the following steps.
1. From the Red Hat OpenShift Container Platform menu, under Workloads, click Deployments.
2. In your car-connector-config deployment, on the YAML tab, change the replicas scale from 1 to 0, and click Save.
```
replicas: 0
```
3. From the Red Hat OpenShift Container Platform menu, under Workloads, click CronJobs.
4. In your cp4s-car-<unique_ID> cron job, click the YAML tab.
5. Edit the connector cron job YAML file to include the following variables in the containers > resources > env section of the file, and click Save.
```
- name: DEBUG
value: 'true'
```
To enable debug level logging by using kubectl, complete the following steps.
1. From the command line, run the following command to change the scale from 1 to 0 in your car-connector-config deployment.
```
kubectl scale deploy car-connector-config --replicas=0 -n cp4s
```
2. To view the connector cron job YAML file, run the following command.
```
kubectl edit cronjob cp4s-car-<unique_ID> -o yaml -n cp4s
```
3. To edit the connector cron job YAML file, type i.
4. Edit the connector cron job YAML file to include the following variables in the containers > resources > env section of the file.
```
- name: DEBUG
value: 'true'
```
5. To save your changes, type :wq, and press Enter.
To enable debug level logging by using oc, complete the following steps.
1. From the command line, run the following command to change the scale from 1 to 0 in your car-connector-config deployment.
```
oc scale dc car-connector-config --replicas=0 -n cp4s
```
2. To view the connector cron job YAML file, run the following command.
```
oc edit cronjob cp4s-car-<unique_ID> -o yaml -n cp4s
```
3. To edit the connector cron job YAML file, type i.
4. Edit the connector cron job YAML file to include the following variables in the containers > resources > env section of the file.
```
- name: DEBUG
value: 'true'
```
5. To save your changes, type :wq, and press Enter.
Change the replicas scale in your car-connector-config deployment to its original value of 1 when you finish the debugging process.