Editing NLog

Keyfactor Command provides extensive logging for visibility and troubleshooting. For more information about troubleshooting, see Troubleshooting.

By default, Keyfactor Command places its log files in the C:\Keyfactor\logs directory, generates logs at the "Info" logging level, and stores the primary logs for two days before deleting them. If you wish to change these defaults you can open the configuration file for each type of log on each Keyfactor Command server where you wish to adjust logging, and edit the file in a text editor (e.g. Notepad) using the "Run as administrator" option. Each Keyfactor component has its own NLog configuration file and NLog logging output path.

Note:  By default, the filename for each component log is unique. This allows you to isolate and research issues on a component-by-component basis by viewing a specific log file. Alternatively, you may wish to change the default output filename to be the same for all logging components so all activity is reported in a single log file. You will note that the default Audit and Alert filenames for each component (for those components that log audits or alerts) are the same so that all activity is logged in the same file across the platform for this reason.
Tip:  If you use the default naming convention, and want to review an event that happened in the management portal, for instance, you would look in the Command_APIClosed A set of functions to allow creation of applications. Keyfactor offers the Keyfactor API, which allows third-party software to integrate with the advanced certificate enrollment and management features of Keyfactor Command._Log.txt and/or the Command_Portal_Log.txt.
Important:  If you do choose to name the log files the same across the platform, it is recommended that you also set the maxArchiveFiles values the same in each Nlog config file. If there is a different value for maxArchiveFiles for files with the same filename/location, the smallest value will override all others.

To make changes to your NLog configuration:

  1. On each Keyfactor Command server where you wish to adjust logging, open a text editor (e.g. Notepad) using the "Run as administrator" option.

  2. In the text editor, browse to open the desired Nlog.config file for the appropriate Keyfactor components. The files are located in application subdirectories under the installed directory, which are the following directories by default:

    • C:\Program Files\Keyfactor\Keyfactor Platform\WebConsole\NLog_Portal.config

      The Portal file is for logging any activity to do with the Keyfactor Command Management Portal, including users connecting to the portal, loading various pages in the portal, and taking actions.

      Note:  Many actions taken in the Keyfactor Command Management Portal are carried out using the Keyfactor API and Keyfactor is migrating the product to use the Keyfactor API more and more, so this file will have less and less activity going forward. See C:\Program Files\Keyfactor\Keyfactor Platform\KeyfactorAPI\NLog_KeyfactorAPI.config.

      The Portal log is for logging any activity to do with the Keyfactor Command web portal. The fields you may wish to edit are:

      • fileName="C:\Keyfactor\logs\Command_Portal_Log.txt"

        The path and file name of the active Keyfactor Command portal log file.

        Important:  If you choose to change the path for storage of the log files, you will need to create the new directory (e.g. D:\KeyfactorLogs) and grant both the service account under which the Keyfactor Command Service is running and the service account under which the IIS application pool for Keyfactor Command is running full control permissions on this directory. These roles may be served by the same service account.
      • archiveFileName="C:\Keyfactor\logs\Command_Portal_Log_Archive_{#}.txt"

        The path and file name of previous days’ Keyfactor Command portal log files. Keyfactor Command rotates log files daily and names the previous files using this naming convention.

      • fileName="C:\Keyfactor\logs\Command_Alert_Log.txt"

        The path and file name of the active Keyfactor Command portal log file for alerting events. This entry is found on servers with the Keyfactor Command Service installed. Info level messages are written to this log whenever alerts (certificate expiration, pending certificate request, issued certificate, denied certificate request, or revocation monitoring) are run either as scheduled tasks or as tests. The log messages include the type of alert (e.g. expiration alert), the recipient of the alert (if an email was scheduled to be sent), and the alert subject line. You can change the level of logging in the log line that references writeTo="alertlogfile". These logs are generated separately from the general portal events to allow for separate tracking and log shipping of alerting events. By default, the alert log filename/location for all components is the same to allow for a central source for tracking alert events across the platform.

      • archiveFileName="C:\Keyfactor\logs\Command_Alert_Log_Archive_{#}.txt""

        The path and file name of previous days’ Keyfactor Command portal log files for alert events.

      • fileName="C:\Keyfactor\logs\Command_Audit_Log.txt"

        The path and file name of the active Keyfactor Command portal log file for auditable events. These logs are generated separately from the general portal events to allow for separate tracking of auditable events. By default, the audit log filename/location for all components is the same to allow for a central source for tracking auditable events across the platform.

      • archiveFileName="C:\Keyfactor\logs\Command_Audit_Log_Archive_{#}.txt""

        The path and file name of previous days’ Keyfactor Command portal log files for auditable events.

      • name="EmailAlertLogger" minlevel="Info" writeTo="alertlogfile"

        The level of log detail that should be generated for alert events and written to the alert logs.

      • maxArchiveFiles="10"

        The number of archive files to retain before deletion. This field is listed multiple times in the NLog_Portal.config file on a server with the Keyfactor Command Service installed—once for the main logging section, once for the alert logging section, and once for the audit logging section. The default number of files to retain is 10 for the main log and the synchronization log but 14 for the alert log and audit log. The alert and audit logs are small by default, and retaining a larger number of them shouldn't create a disk space issue.

      • archiveAboveSize="52428800"

        The maximum file size of each log file. Once a log file reaches this size (50 MB by default), it will be rotated to archive even if the end of the day has not been reached.

      • name="*" minlevel="Info" writeTo="logfile"

        The level of log detail that should be generated. This line applies to all the logs in the portal file. The default "Info" level logs error and some informational data but at a minimal level to avoid generating large log files. For troubleshooting, it may be desirable to set the logging level to "Debug" or "Trace". Available log levels (in order of increasing verbosity) are:

        • OFF – No logging
        • FATAL – Log severe errors that cause early termination
        • ERROR – Log severe errors and other runtime errors or unexpected conditions that may not cause early termination
        • WARN – Log errors and use of deprecated APIs, poor use of APIs, "almost" errors, and other runtime situations that are undesirable or unexpected but not necessarily "wrong"
        • INFO – Log all of the above plus runtime events (startup/shutdown)
        • DEBUG – Log all of the above plus detailed information on the flow through the system
        • TRACE – Maximum log information—this option can generate VERY large log files

      Figure 410: Nlog_Portal.config

    • C:\Program Files\Keyfactor\Keyfactor Platform\KeyfactorAPI\NLog_KeyfactorAPI.config

      The KeyfactorAPI file is the primary file for logging activity related to making requests with the Keyfactor API. Since many of the functions in the Management Portal use the Keyfactor API, this log also includes activity related to running the Management Portal.

      The KeyfactorAPI file is the primary file for logging activity related to running Keyfactor Command API. The fields you may wish to edit are:

      • fileName="C:\Keyfactor\logs\Command_API_Log.txt"

        The path and file name of the active Keyfactor Command primary log file.

        Important:  If you choose to change the path for storage of the log files, you will need to create the new directory (e.g. D:\KeyfactorLogs) and grant both the service account under which the Keyfactor Command Service is running and the service account under which the IIS application pool for Keyfactor Command is running full control permissions on this directory. These roles may be served by the same service account.
      • archiveFileName="c:\Keyfactor\logs\Command_API_Log_Archive_{#}.txt"

        The path and file name of previous days’ Keyfactor Command primary log files. Keyfactor Command rotates log files daily and names the previous files using this naming convention.

      • fileName="C:\Keyfactor\logs\Command_Alert_Log.txt"

        The path and file name of the active Keyfactor Command primary log file for alerting events. This entry is only found on servers with the Keyfactor Command Service installed. Info level messages are written to this log whenever alerts (certificate expiration, pending certificate request, issued certificate, denied certificate request, or revocation monitoring) are run either as scheduled tasks or as tests. The log messages include the type of alert (e.g. expiration alert), the recipient of the alert (if an email was scheduled to be sent), and the alert subject line. You can change the level of logging in the log line that references writeTo="alertlogfile". These logs are generated separately from the primary log events to allow for separate tracking and log shipping of alerting events. By default, the alert log filename/location for all components is the same to allow for a central source for tracking alert events across the platform.

      • archiveFileName="c:\Keyfactor\logs\Command_Alert_Log_Archive_{#}.txt""

        The path and file name of previous days’ Keyfactor Command primary log files for alert events.

      • fileName="C:\Keyfactor\logs\Command_Audit_Log.txt"

        The path and file name of the active Keyfactor Command primary log file for auditable events. These logs are generated separately from the primary log events to allow for separate tracking of auditable events. By default, the audit log filename/location for all components is the same to allow for a central source for tracking auditable events across the platform.

      • archiveFileName="c:\Keyfactor\logs\Command_Audit_Log_Archive_{#}.txt""

        The path and file name of previous days’ Keyfactor Command primary log files for auditable events.

      • name="EmailAlertLogger" minlevel="Info" writeTo="alertlogfile"

        The level of log detail that should be generated for alert events and written to the alert logs.

      • maxArchiveFiles="10"

        The number of archive files to retain before deletion. This field is listed multiple times in the NLog_KeyfactorAPI.config file —once for the main logging section, once for the alert logging section, and once for the audit logging section. The default number of files to retain is 10 for the main log and the synchronization log but 14 for the alert log and audit log. The alert and audit logs are small by default, and retaining a larger number of them shouldn't create a disk space issue.

      • archiveAboveSize="52428800"

        The maximum file size of each log file. Once a log file reaches this size (50 MB by default), it will be rotated to archive even if the end of the day has not been reached.

      • name="*" minlevel="Info" writeTo="logfile"

        The level of log detail that should be generated. This line applies to all the logs of the KeyfactorAPI file. The default "Info" level logs error and some informational data but at a minimal level to avoid generating large log files. For troubleshooting, it may be desirable to set the logging level to "Debug" or "Trace". Available log levels (in order of increasing verbosity) are:

        • OFF – No logging
        • FATAL – Log severe errors that cause early termination
        • ERROR – Log severe errors and other runtime errors or unexpected conditions that may not cause early termination
        • WARN – Log errors and use of deprecated APIs, poor use of APIs, "almost" errors, and other runtime situations that are undesirable or unexpected but not necessarily "wrong"
        • INFO – Log all of the above plus runtime events (startup/shutdown)
        • DEBUG – Log all of the above plus detailed information on the flow through the system
        • TRACE – Maximum log information—this option can generate VERY large log files

      Figure 411: Nlog_KeyfactorAPI.config

    • C:\Program Files\Keyfactor\Keyfactor Platform\Service\NLog_TimerService.config

      The Timer Service file logs activity related to scheduled and automated events within Keyfactor Command such as CAClosed A certificate authority (CA) is an entity that issues digital certificates. Within Keyfactor Command, a CA may be a Microsoft CA or a Keyfactor gateway to a cloud-based or remote CA. synchronization, scheduled alerts, and scheduled reports.

      The Timer Service file logs activity related to scheduled and automated events within Keyfactor Command and includes the CA sync logs. The fields you may wish to edit are:

      • fileName="C:\Keyfactor\logs\Command_Service_Log.txt"

        The path and file name of the active Keyfactor Command timer service log file.

        Important:  If you choose to change the path for storage of the log files, you will need to create the new directory (e.g. D:\KeyfactorLogs) and grant both the service account under which the Keyfactor Command Service is running and the service account under which the IIS application pool for Keyfactor Command is running full control permissions on this directory. These roles may be served by the same service account.
      • archiveFileName="C:\Keyfactor\logs\Command_Service_Log_Archive_{#}.txt"

        The path and file name of previous days’ Keyfactor Command timer service log files. Keyfactor Command rotates log files daily and names the previous files using this naming convention.

      • fileName="C:\Keyfactor\logs\Command_Alert_Log.txt"

        The path and file name of the active Keyfactor Command timer service log file for alerting events. This entry is only found on servers with the Keyfactor Command Service installed. Info level messages are written to this log whenever alerts (certificate expiration, pending certificate request, issued certificate, denied certificate request, or revocation monitoring) are run either as scheduled tasks or as tests. The log messages include the type of alert (e.g. expiration alert), the recipient of the alert (if an email was scheduled to be sent), and the alert subject line. You can change the level of logging in the log line that references writeTo="alertlogfile". These logs are generated separately from the general timer service events to allow for separate tracking and log shipping of alerting events. By default, the alert log filename/location for all components is the same to allow for a central source for tracking alert events across the platform.

      • archiveFileName="C:\Keyfactor\logs\Command_Alert_Log_Archive_{#}.txt""

        The path and file name of previous days’ Keyfactor Command timer service log files for alert events.

      • fileName="C:\Keyfactor\logs\Command_Audit_Log.txt"

        The path and file name of the active Keyfactor Command timer service log file for auditable events. These logs are generated separately from the general timer service events to allow for separate tracking of auditable events. By default, the audit log filename/location for all components is the same to allow for a central source for tracking auditable events across the platform.

      • archiveFileName="C:\Keyfactor\logs\Command_Audit_Log_Archive_{#}.txt""

        The path and file name of previous days’ Keyfactor Command timer service log files for auditable events.

      • name="EmailAlertLogger" minlevel="Info" writeTo="alertlogfile"

        The level of log detail that should be generated for alert events and written to the alert logs.

      • maxArchiveFiles="10"

        The number of archive files to retain before deletion. This field is listed multiple times in the NLog_TimerService.config file on a server with the Keyfactor Command Service installed—once for the main logging section, once for the alert logging section, and once for the audit logging section. The default number of files to retain is 10 for the main log and the synchronization log but 14 for the alert log and audit log. The alert and audit logs are small by default, and retaining a larger number of them shouldn't create a disk space issue.

      • archiveAboveSize="52428800"

        The maximum file size of each log file. Once a log file reaches this size (50 MB by default), it will be rotated to archive even if the end of the day has not been reached.

      • name="*" minlevel="Info" writeTo="logfile"

        The level of log detail that should be generated. This line applies to all the logs of the timer service file. The default "Info" level logs error and some informational data but at a minimal level to avoid generating large log files. For troubleshooting, it may be desirable to set the logging level to "Debug" or "Trace". Available log levels (in order of increasing verbosity) are:

        • OFF – No logging
        • FATAL – Log severe errors that cause early termination
        • ERROR – Log severe errors and other runtime errors or unexpected conditions that may not cause early termination
        • WARN – Log errors and use of deprecated APIs, poor use of APIs, "almost" errors, and other runtime situations that are undesirable or unexpected but not necessarily "wrong"
        • INFO – Log all of the above plus runtime events (startup/shutdown)
        • DEBUG – Log all of the above plus detailed information on the flow through the system
        • TRACE – Maximum log information—this option can generate VERY large log files

      Figure 412: Nlog_TimerService.config

    • C:\Program Files\Keyfactor\Keyfactor Platform\WebAgentServices\NLog_Orchestrators.config

      The Orchestrators, or OrchestratorsAPI, file logs activity related to Keyfactor Orchestrators API. Look here for messages related to orchestrators communicating with Keyfactor Command.

      The Orchestrators, or OrchestratorsAPI, file logs activity related to orchestrators API. The fields you may wish to edit are:

      • fileName="C:\Keyfactor\logs\Command_OrchestratorsAPI_Log.txt"

        The path and file name of the active Keyfactor Command orchestrators log file.

        Important:  If you choose to change the path for storage of the log files, you will need to create the new directory (e.g. D:\KeyfactorLogs) and grant both the service account under which the Keyfactor Command Service is running and the service account under which the IIS application pool for Keyfactor Command is running full control permissions on this directory. These roles may be served by the same service account.
      • archiveFileName="C:\Keyfactor\logs\Command_OrchestratorsAPI_Log_Archive_{#}.txt"

        The path and file name of previous days’ Keyfactor Command orchestrators log files. Keyfactor Command rotates log files daily and names the previous files using this naming convention.

      • fileName="C:\Keyfactor\logs\Command_Alert_Log.txt"

        The path and file name of the active Keyfactor Command orchestrators log file for alerting events. This entry is found on servers with the Keyfactor Command Service installed. Info level messages are written to this log whenever alerts (certificate expiration, pending certificate request, issued certificate, denied certificate request, or revocation monitoring) are run either as scheduled tasks or as tests. The log messages include the type of alert (e.g. expiration alert), the recipient of the alert (if an email was scheduled to be sent), and the alert subject line. You can change the level of logging in the log line that references writeTo="alertlogfile". These logs are generated separately from the general orchestratorClosed Keyfactor orchestrators perform a variety of functions, including managing certificate stores and SSH key stores. events to allow for separate tracking and log shipping of alerting events. By default, the alert log filename/location for all components is the same to allow for a central source for tracking alert events across the platform.

      • archiveFileName="C:\Keyfactor\logs\Command_Alert_Log_Archive_{#}.txt""

        The path and file name of previous days’ Keyfactor Command orchestrators log files for alert events.

      • fileName="C:\Keyfactor\logs\Command_Audit_Log.txt"

        The path and file name of the active Keyfactor Command orchestrators log file for auditable events. These logs are generated separately from the general orchestrator events to allow for separate tracking of auditable events. By default, the audit log filename/location for all components is the same to allow for a central source for tracking auditable events across the platform.

      • archiveFileName="C:\Keyfactor\logs\Command_Audit_Log_Archive_{#}.txt""

        The path and file name of previous days’ Keyfactor Command orchestrators log files for auditable events.

      • name="EmailAlertLogger" minlevel="Info" writeTo="alertlogfile"

        The level of log detail that should be generated for alert events and written to the alert logs.

      • maxArchiveFiles="10"

        The number of archive files to retain before deletion. This field is listed multiple times in the NLog_Orchestrators.config file on a server with the Keyfactor Command Service installed—once for the main logging section, once for the alert logging section, and once for the audit logging section. The default number of files to retain is 10 for the main log and the synchronization log but 14 for the alert log and audit log. The alert and audit logs are small by default, and retaining a larger number of them shouldn't create a disk space issue.

      • archiveAboveSize="52428800"

        The maximum file size of each log file. Once a log file reaches this size (50 MB by default), it will be rotated to archive even if the end of the day has not been reached.

        Note:  The default value for the archiveAboveSize setting was significantly larger in versions of Keyfactor Command prior to 7.5. In addition, the default maxArchiveFiles value was 2 for the main and CA synchronization logging sections. In environments where the logging level is consistently set at debug level or greater, this change may result in the generation of several log files per day.
      • name="*" minlevel="Info" writeTo="logfile"

        The level of log detail that should be generated. This line applies to all the logs of the orchestrators file. The default "Info" level logs error and some informational data but at a minimal level to avoid generating large log files. For troubleshooting, it may be desirable to set the logging level to "Debug" or "Trace". Available log levels (in order of increasing verbosity) are:

        • OFF – No logging
        • FATAL – Log severe errors that cause early termination
        • ERROR – Log severe errors and other runtime errors or unexpected conditions that may not cause early termination
        • WARN – Log errors and use of deprecated APIs, poor use of APIs, "almost" errors, and other runtime situations that are undesirable or unexpected but not necessarily "wrong"
        • INFO – Log all of the above plus runtime events (startup/shutdown)
        • DEBUG – Log all of the above plus detailed information on the flow through the system
        • TRACE – Maximum log information—this option can generate VERY large log files

      Figure 413: Nlog_Orchestrators.config

    • C:\Program Files\Keyfactor\Keyfactor Platform\Configuration\NLog_Configuration.config

      The Configuration file logs activity related to running the Keyfactor Command configuration wizard only. It may be useful to increase the logging level on this one if you are experiencing installation or upgrade issues.

      The Configuration file logs activity related to running the Keyfactor Command configuration wizard only. The fields you may wish to edit are:

      • fileName="C:\Keyfactor\logs\Command_Configuration_Log.txt"

        The path and file name of the active Keyfactor Command configuration wizard log file.

        Important:  If you choose to change the path for storage of the log files, you will need to create the new directory (e.g. D:\KeyfactorLogs) and grant both the service account under which the Keyfactor Command Service is running and the service account under which the IIS application pool for Keyfactor Command is running full control permissions on this directory. These roles may be served by the same service account.
      • archiveFileName="C:\Keyfactor\logs\Command_Configuration_Log_Archive_{#}.txt"

        The path and file name of previous days’ Keyfactor Command configuration wizard log files. Keyfactor Command rotates log files daily and names the previous files using this naming convention.

      • fileName="C:\Keyfactor\logs\Command_Audit_Log.txt"

        The path and file name of the active Keyfactor Command log file for auditable configuration wizard events. These logs are generated separately from the configuration log events to allow for separate tracking of auditable events. By default, the audit log filename/location for all components is the same to allow for a central source for tracking auditable events across the platform.

      • archiveFileName="C:\Keyfactor\logs\Command_Audit_Log_Archive_{#}.txt""

        The path and file name of previous days’ Keyfactor Command log files for auditable configuration wizard events.

      • maxArchiveFiles="10"

        The number of archive files to retain before deletion. This field is listed multiple times in the NLog_Configuration.config file on a server —once for the main logging section and once for the audit logging section. The default number of files to retain is 10 for the main log and 14 for the audit log. The audit logs are small by default, and retaining a larger number of them shouldn't create a disk space issue.

      • archiveAboveSize="52428800"

        The maximum file size of each log file. Once a log file reaches this size (50 MB by default), it will be rotated to archive even if the end of the day has not been reached.

      • name="*" minlevel="Info" writeTo="logfile"

        The level of log detail that should be generated. This line applies to all the logs in the configuration file. The default "Info" level logs error and some informational data but at a minimal level to avoid generating large log files. For troubleshooting, it may be desirable to set the logging level to "Debug" or "Trace". Available log levels (in order of increasing verbosity) are:

        • OFF – No logging
        • FATAL – Log severe errors that cause early termination
        • ERROR – Log severe errors and other runtime errors or unexpected conditions that may not cause early termination
        • WARN – Log errors and use of deprecated APIs, poor use of APIs, "almost" errors, and other runtime situations that are undesirable or unexpected but not necessarily "wrong"
        • INFO – Log all of the above plus runtime events (startup/shutdown)
        • DEBUG – Log all of the above plus detailed information on the flow through the system
        • TRACE – Maximum log information—this option can generate VERY large log files

      Figure 414: Nlog_Configuration.config

    • C:\Program Files\Keyfactor\Keyfactor Platform\WebAPI\NLog_ClassicAPI.config

      The ClasssicAPI file logs activity involving the ClassicAPI from Keyfactor Command. You will only need to modify the logging settings on this one if you have upgraded from a previous version of Keyfactor Command and have implemented a custom application built with the Classic API.

      The ClasssicAPI file logs activity related to invoking the ClassicAPI from Keyfactor Command. The fields you may wish to edit are:

      • fileName="C:\Keyfactor\logs\Command_ClassicAPI_Log.txt"

        The path and file name of the active Keyfactor Command classic API log file.

        Important:  If you choose to change the path for storage of the log files, you will need to create the new directory (e.g. D:\KeyfactorLogs) and grant both the service account under which the Keyfactor Command Service is running and the service account under which the IIS application pool for Keyfactor Command is running full control permissions on this directory. These roles may be served by the same service account.
      • archiveFileName="C:\Keyfactor\logs\Command_ClassicAPI_Log_Archive_{#}.txt"

        The path and file name of previous days’ Keyfactor Command classic API log files. Keyfactor Command rotates log files daily and names the previous files using this naming convention.

      • fileName="C:\Keyfactor\logs\Command_Alert_Log.txt"

        The path and file name of the active Keyfactor Command classic API log file for alerting events. This entry is found on servers with the Keyfactor Command Service installed. Info level messages are written to this log whenever alerts (certificate expiration, pending certificate request, issued certificate, denied certificate request, or revocation monitoring) are run either as scheduled tasks or as tests. The log messages include the type of alert (e.g. expiration alert), the recipient of the alert (if an email was scheduled to be sent), and the alert subject line. You can change the level of logging in the log line that references writeTo="alertlogfile". These logs are generated separately to allow for separate tracking and log shipping of alerting events. By default, the alert log filename/location for all components is the same to allow for a central source for tracking alert events.

      • archiveFileName="C:\Keyfactor\logs\Command_Alert_Log_Archive_{#}.txt""

        The path and file name of previous days’ Keyfactor Command classic API log files for alert events.

      • fileName="C:\Keyfactor\logs\Command_Audit_Log.txt"

        The path and file name of the active Keyfactor Command classic API log file for auditable events. These logs are generated separately from the general classic API events to allow for separate tracking auditable events. By default, the audit log filename/location for all components is the same to allow for a central source for tracking auditable events across the platform.

      • archiveFileName="C:\Keyfactor\logs\Command_Audit_Log_Archive_{#}.txt""

        The path and file name of previous days’ Keyfactor Command classic API log files for auditable events.

      • name="EmailAlertLogger" minlevel="Info" writeTo="alertlogfile"

        The level of log detail that should be generated for alert events and written to the alert logs.

      • maxArchiveFiles="10"

        The number of archive files to retain before deletion. This field is listed multiple times in the Nlog_ClassicAPI.config file —once for the main logging section, once for the alert logging section, and once for the audit logging section. The default number of files to retain is 10 for the main log and the synchronization log but 14 for the alert log and audit log. The alert and audit logs are small by default, and retaining a larger number of them shouldn't create a disk space issue.

      • archiveAboveSize="52428800"

        The maximum file size of each log file. Once a log file reaches this size (50 MB by default), it will be rotated to archive even if the end of the day has not been reached.

      • name="*" minlevel="Info" writeTo="logfile"

        The level of log detail that should be generated. This line applies to all the logs of the classicAPI file. The default "Info" level logs error and some informational data but at a minimal level to avoid generating large log files. For troubleshooting, it may be desirable to set the logging level to "Debug" or "Trace". Available log levels (in order of increasing verbosity) are:

        • OFF – No logging
        • FATAL – Log severe errors that cause early termination
        • ERROR – Log severe errors and other runtime errors or unexpected conditions that may not cause early termination
        • WARN – Log errors and use of deprecated APIs, poor use of APIs, "almost" errors, and other runtime situations that are undesirable or unexpected but not necessarily "wrong"
        • INFO – Log all of the above plus runtime events (startup/shutdown)
        • DEBUG – Log all of the above plus detailed information on the flow through the system
        • TRACE – Maximum log information—this option can generate VERY large log files

      Figure 415: Nlog_ClassicAPI.config

      • Once configured, the log file location defined will look similar to this:

      Figure 416: C:\Keyfactor\logs logs

  3. Change the respective files and save your changes.