Logging

Learn how to store logs for Billing Data Service (BDS).

Related documentation:

• Billing Data Service Release Notes

Beta Program

Genesys Multicloud CX private edition is being released to pre-approved customers as part of the Beta Program. Please note that the documentation and the product are subject to change. For more details about the program, please contact your Genesys representative.

BDS writes all logs to the standard output. 

Viewing logs

1. Execute the following command to get the pod name:

   kubectl -n bds get po

   NAME                             READY   STATUS      RESTARTS   AGE
   
   bds-t2023-2023-1624633200-w8nh5  0/1     Completed  0          34m

   Where the NAME string is composed of the following elements: bds-t<tenant id>-<tenant id>-<job start linux time>-<random value>

2. Execute the following command to check the logs:

   kubectl logs bds-pod-<name>

   Where <name> is the pod name.

   For example:

   kubectl logs bds-pod-wn8bx

Setting the log level

Optionally, you can set the log level using the BDS_LOG_LEVEL environment variable. Acceptable values are:

CRITICAL, 50, ERROR, 40, WARNING, 30, INFO, 20, DEBUG, 10,NOTSET, 0.

If you do not set a value, BDS reads the default value from gvars.py. If gvars.py contains no value, BDS uses the default value (DEBUG).