![]() This file was called um_log in earlier product versions. auth.log (on the Security Console only): This file captures each logon or logoff as well as authentication events, such as authentication failures and lockouts.The file was called access_log in earlier product versions. This is useful for monitoring API use and troubleshooting API issues. At the INFO level, access.log captures useful information about API events, such as APIs that are being called, the API version, and the IP address of the API client. access.log (on the Security Console only): This file captures information about resources that are being accessed, such as pages in the Web interface.Log files are located in /nsc/logs of the directory you installed on the Security Console and /nse/logs of the directory you installed on Scan Engines. Locating each log file and understanding its purpose The section does not cover the scan log, which is related to scan events. Log files can also be useful for routine maintenance and debugging purposes. If you are encountering problems with the Security Console or Scan Engine, you may find it helpful to consult log files for troubleshooting. If you do need to contact Technical Support, this section will help you gather the information that Support needs to assist you. This section provides descriptions of problems commonly encountered when using the application and guidance for dealing with them. Interrupted connection to the update server.Tip for addressing delayed scan operations.Addressing failure to refresh a session.Retrieve the collected Enhanced logging data and send it to Technical Support.Run an authenticated scan with the Enhanced logging-enabled template. ![]() Enable Enhanced logging in a custom scan template. ![]() Troubleshooting scan accuracy issues with logs. ![]()
0 Comments
Leave a Reply. |