Change service director (named) log levels

Log on as root or egoadmin.

Log levels for the service director are set differently than log levels for the service controller, Platform Management Console, and web service gateway. Logged by the BIND DNS server, the service director logs information gathered during the updating and querying of service instance location.

The default log level for the service director is set to severity debug 3. If your system is running well, you likely want to set the severity to something lower. Only use severity debug [level], which generates a lot of messages, for troubleshooting or debugging purposes. In this case, you may wish to reduce the associated log class as well.

  1. To reduce the amount of detail logged to named.log, open the file from this location:
    • Windows: EGO_TOP\eservice\esd\conf\named\conf\named.conf

    • Linux: EGO_TOP/eservice/esd/conf/named/conf/named.conf

  2. Locate the section on logging, and the subsection on severity.

    };logging {        channel my_file {               file "named.log" versions 2 size 10m;               severity debug 3;               print-time yes;               print-category yes;                     };        category default {my_file;};};

  3. Change the severity log class to a lower class.

    Choose from critical, error, warning, notice, info, debug, or dynamic (where critical logs only the most critical event information, resulting in the least number of log entries).

    If you choose to keep the default log class (debug), you can lower the log level from 3 to 1 (where 1 results in the fewest messages and the lowest detail level of logged debug information).

  4. Save the file.