Usage Engine provides options to further enhance the debugging of your Pod(s). There are parameters that can be customized from the values.yaml file and these will allow you to customize your own format of the log message or even to specify the severity level of the log messages that will be stored in the log files.

...

• platform.log
• ec.log
• webdesktop.log

Debugging for Platform and Web Desktop

This section will cover the parameters and information that you will come across when customizing your debugging parameters for the Platform and Web Desktop.

JMX Debug

For JMX Debug, you will need to set the following parameters under the debug section in the values.yaml files from the helm chart in order to customize the log files accordingly.

...

mediationzone / values.yaml:
platform:
 ...
 ...
  # Debugging for JMX and logging
  # JMX refers to .Values.debug.JMX.port
  debug:
    jmx:
      enabled: true

webdesktop:
 ...
 ...
  # Debugging for JMX and logging
  # JMX refers to .Values.debug.JMX.port
  debug:
    jmx:
      enabled: true

Debugging for ECD

If you have had the debug parameters defined and enabled on your platform, ECD will automatically retrieve the parameters and the values from the platform and apply it into your EC deployment. However, you will still be required to expose the JMX port when setting up the ECD.