How To: Enable Enhanced Logging for the New Experience Admin Console

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected: 9.3, 19.07 and later

     

    Overview

    When troubleshooting New Experience Admin Console issues, an additional, more verbose log can be enabled beyond the default log in D:\Secureauth\ApplicationApi. If AdminApiLogs is missing because of an incorrect Nlog.config rather than by design, see Troubleshooting: AdminAPILogs Folder Is Missing Due to an Incorrect Nlog.config instead.

     

    Enable the Enhanced AdminApi Log

    1. Create D:\Secureauth\AdminApiLogs if it doesn't already exist.
    2. Back up D:\Secureauth\Api\nlog.config.
    3. Replace its contents with:
    <?xml version="1.0" encoding="utf-8" ?>
    <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://www.nlog-project.org/schemas/NLog.xsd NLog.xsd"
          autoReload="true"
          throwExceptions="false"
          internalLogLevel="Off" internalLogFile="c:\temp\nlog-internal.log">
    
    <targets>
    <target name="logfile" xsi:type="File" fileName="D:\SecureAuth\AdminApiLogs\AdminApiLog.txt"
            layout="${date:universalTime=True}|${level}|${logger}|${message}|${exception:format=tostring}"/>
    </targets>
    
    <rules>
    <logger name="*" minlevel="Debug" writeTo="logfile" />
    </rules>
    </nlog>
    1. The new log appears as D:\SecureAuth\AdminApiLogs\AdminApiLog.txt.


     

    Special Considerations

    When troubleshooting, use this file together with D:\SecureAuth\ApplicationApi\nlog-all-YYYY-MM-DD.log, and supply both if requested by SecureAuth Technical Support.


     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.