SF Monk

Hope you have read Part I of this series !! In this part we'll understand how to read log file. Once you capture a log file and open it, you can get all information from first line itself. First line of log gives information about the log categories and levels and   Second line gives User Information EXECUTION_STARTED marks the start of transaction. CODE_UNIT_STARTED and CODE_UNIIT_FINISHED marks start and end of particular code unit which was executed during transaction. Using this you can check what has happened when particular unit of code executed. Units of code include, but are not limited to, the following: Triggers Workflow invocations and time-based workflow Validation rules Approval processes Apex lead convert @future method invocations Web service invocations executeAnonymous calls Visualforce property accesses on Apex controllers Visualforce actions on Apex controllers Execution of the batch Apex start and finish methods, and each ex...

If you are ready to accept that your code can run into error, then debug logs can help you to find out the victim. Debug logs give all required information of a transaction to find out what is exactly happening when you perform any kind of action in Salesforce which includes database operation, system processes.You can set debug logs for users, classes and triggers. Before moving ahead with how to capture debug logs, let’s understand few related terms which we will use while setting debug logs :  When monitoring debug logs you can specify what you want track or capture in that file. For this Log Category and Log Level helps. Log Category :    With this you can mention what type of information you want to be logged, such as whether you want to get information about Apex or DML operations etc.            Below are the different log categories –         Category Description Database This gi...