Changing the log level of Audit Logs

Only users with the partner or support permission can change the log level of Audit logs.

Changing the Fabric Proxy log level

  1. Stop the running zookeeper process with the commands sudo sv stop zookeeper and sudo /opt/commander/installed/zookeeper/bin/zkServer.sh stop.

  2. Edit the file /opt/commander/installed/zookeeper/conf/log4j.properties using the command sudo vi /opt/commander/installed/zookeeper/conf/log4j.properties. Replace the first line with the command log4j.rootCategory=INFO, file. Change the log level from INFO to the required log level like DEBUG, WARN or TRACE.

  3. Start the service using the sudo sv start zookeeper command.

Changing the Fabric Storage log level

  1. Edit the file /opt/commander/etc/hadoop/log4j.properties using the command sudo vi /opt/commander/etc/hadoop/log4j.properties. Replace the first line with the command log4j.rootCategory=INFO, file. Change the log level from INFO to the required log level like DEBUG, WARN or TRACE.

  2. Reboot the system for the changes to take effect.

Changing the API Server log level

  1. Stop the tomcat service using the sudo docker stop directorapi command.

  2. Edit the following files:

    /opt/commander/etc/config/{configapi,monitorapi,governingapi}.properties.

    Choose configapi, monitorapi or governingapi according to the requirements.

    For example,

    • Execute the following command to change the loglevel of configapi:

      sudo vi /opt/commander/etc/config/configapi/configapi.properties

    • Replace the first line with the command log4j.rootCategory=INFO, file.

    • Change the log level from INFO to the required log level like DEBUG, WARN or TRACE.

  3. Start the tomcat service using the sudo docker start directorapi command.


Helpful?

We are glad this guide helped.


Please don't include any personal information in your comment

Contact Support