Log files can be extremely useful for troubleshooting. They’re also a big help for finding the root cause of an incident. Logs let us track of where a problem occurred, and when. Before, with the Get 4D folder command, you could easily access the folder containing all the logs. Now, 4D v16 R6 makes easy to find a particular log file, thanks to the enhancement of the Get 4D file command.
As a server administrator, it’s now easy to monitor your server based on log file information. For instance, you can monitor your server activity by checking the Request log file content, which lists all standard requests carried out by the 4D Server machine or the 4D remote machine.
Here is the list of selectors which have been added to the Get 4D file command to simplify log file access:
- Request log file
- Debug log file
- Backup log file
- Verification log file
- Compacting log file
- Repair log file
- HTTP log file
- Build application log file
Open debug log
The following code opens the Debug log file containing every operation that occurred at the 4D programming level:
$logFilePath:=Get 4D file(Debug log file)
Want to know more about log files? Check out this article in the documentation.