How to access a Foglight Agent Manager (FglAM) log file (4228388)

General details about the FglAM log file name

• The filename is in the following format: FglAM_YYYY_MM_DD_HHMMSS_XXX.log and includes the date and time of the last time when the FglAM process (service) was restarted.
• The most recent file of each set (based on the filename) will end with the .log (log file) extension and have the higher incremented value in the last three characters of the main filename.  
• Previous files for the set will be compressed .gz format and they usually will be larger than the other files with the same filename timestamp.

Accessing the file 

Using the FMS UI

Users may need the Administrator role to access this panel

• Navigate to Administration | Agents | Agent Managers
  
• Click the Latest Log File icon in listed Agent Manager row to download copy of the FglAM log through the browser to the local desktop of the user's PC.
  

Opening the file directly on the server

• From a command line (in Linux/Unix) or using Windows Explorer, navigate {FglAM location}\state\default\logs
• Look for the most recent copy of the FMS log named FglAM_YYYY_MM_DD_HHMMSS_XXX.txt
• Open the text file in a text editor (e.g., Vim, Pico, Microsoft Wordpad)

From a FglAM support bundle

• Generate a FglAM support bundle (as described in Knowledgebase article 41911
• Open the Support Bundle and drill down into the state\default\logs folder
• Look for the most recent copy of the FMS log named FglAM_YYYY_MM_DD_HHMMSS_XXX.log
• Open the text file in a text editor (e.g., Vim, Pico, Microsoft Wordpad)

Reviewing the log file

• Note: Large log files such as the FMS log, the Monitoring Policy and Diagnostic Snapshot may be much slower in Windows Notepad due to how Notepad manages files in memory.
• In the text editor, change the content of the wrap the lines (word wrap) for easier error log message reading.
  
• Scroll down to the bottom of the file to find the most recent error messages.
  
• Identify the error message that occurred. The subsequent stack error content can be ignored as it is used exclusively by developers to determine how various subroutines work together during execution of the code.
• Reference this error message in researching the Supportlink knowledgebase or when reaching out to Support for assistance.