How to view debug logs in salesforce


  • To view the debug logs, from the setup option in Salesforce, enter ‘Debug Logs’ in the ‘Quick Find box’, then select ‘Debug Logs’.
  • Once you select the Debug Logs, click the ‘View’ button to examine the log.
  • Click ‘Download’ to download the logs as an XML file.

To view a debug log, from Setup, enter Debug Logs in the Quick Find box, then select Debug Logs. Then click View next to the debug log that you want to examine. Click Download to download the log as an XML file.

How to use debug logs in Salesforce to troubleshoot?

  • Processes created in the Process Builder appear as flows and workflow rules in debug logs. …
  • Record change processes appear as flows of type Workflow. …
  • Immediate actions that are executed in a block are strung together in the flow. …
  • Scheduled actions are executed after a FLOW_WAIT element. …

More items…

How to enable debug logs?

Log on to the computer as a member of the local administrators group. Launch Event Viewer. Select ViewShow Analytic and Debug Logs. Navigate to Event Viewer (Local)Applications and Service LogsMicrosoftUser Experience VirtualizationApp Agent. Right-click on Debug under App Agent and select Enable Log.

What are debug logs and how do I use them?

  • Each debug log must be 20 MB or smaller. …
  • System debug logs are retained for 24 hours. …
  • If you generate more than 1,000 MB of debug logs in a 15-minute window, your trace flags are disabled. …
  • When your org accumulates more than 1,000 MB of debug logs, we prevent users in the org from adding or editing trace flags. …

How do I collect debug logs?

To collect debug logs

  • Right-click on “Debug” node and select “Save all events as”.
  • Choose a location and a file name and Save.
  • Choose “Display information for these languages” and select “English (United States)”.
  • Click “Ok”.

How do I read a debug log?

You can read a debug log by identifying what each column represents.Timestamp—The time when the event occurred. … Event—The event that triggered the debug log entry. … Details—Details about the line of code and the method name where the code was executed.

What is a debug log?

Debug logs are logs with an extended logging level. They can be helpful to support engineers when the application logs are insufficient to investigate an issue. Debug logs can be enabled for both Backup Manager and Recovery Console.

What is debug logs in Salesforce?

A debug log can record database operations, system processes, and errors that occur when executing a transaction or running unit tests. Debug logs can contain information about: Database changes. HTTP callouts.

How do I view integration logs in Salesforce?

You can find the Integration Log by going to Settings > Integration Log, but in most cases you’ll see an alert either in the System Messages Widget or on the Messages area of the main navigation, like this: Clicking on any of the links will bring you to a list of all the integration tasks with uncleared errors.

What is a debug log?

A debug log can record database operations, system processes, and errors that occur when executing a transaction or running unit tests. Debug logs can contain information about: Database changes. HTTP callouts. Apex errors.

How long are debug logs retained?

The log lines can be removed from any location, not just the start of the debug log. System debug logs are retained for 24 hours. Monitoring debug logs are retained for seven days. If you generate more than 1,000 MB of debug logs in a 15-minute window, your trace flags are disabled.

What is debug filtering?

Debug log filtering provides a mechanism for fine-tuning the log verbosity at the trigger and class level. This is especially helpful when debugging Apex logic. For example, to evaluate the output of a complex process, you can raise the log verbosity for a given class while turning off logging for other classes or triggers within a single request.

What is a log line?

Log lines are included inside units of code and indicate which code or rules are being executed. Log lines can also be messages written to the debug log. For example: Log lines are made up of a set of fields, delimited by a pipe ( | ).

Does debug log include time based workflows?

The debug log does not include information from actions triggered by time-based workflows. You can retain and manage debug logs for specific users, including yourself, and for classes and triggers. Setting class and trigger trace flags doesn’t cause logs to be generated or saved.

Debug Logs in Salesforce

Debug logs in Salesforce are the best source of information to uncover what is actually taking place on the platform. These are the best option to track back events that might have happened in the Org. Specifically, if we are doing root cause analysis for a particular problem, we can trace out the root cause from the debug logs.

Use cases of debug logs

Debug logs can be used by the developers for tracing any errors that might have occurred on the application. For example, the application is not stable or it is impacting the performance of the other components, or it might stop responding after a certain user input because exceptions are not defined.

Limitations of the Debug Log

Debug logs are undoubtedly helpful for monitoring the platform, but it has certain limitations as well.

Setting Up the debug logging

Debug logging can be activated for Apex classes & triggers and normal users. For this, trace flags need to be configured along with the debug levels, in the Developer Console. Each trace flag will contain the following:

Debug Log Details

Analyzing the debug log is an art, and might need prior experience as a developer or administrator. However, if you are aware of the components of the debug logs, at least you will be aware, where to look for what. The components of the debug log are mentioned below:

Debug Log Categories

Each debug level includes a debug log level for each of the following log categories. The amount of information logged for each category depends on the log level.

Debug Log Levels

Each debug level includes one of the following log levels for each log category. The levels are listed from lowest to highest. Specific events are logged based on the combination of category and levels. Most events start being logged at the INFO level.

Debug Event Types

The following is an example of what is written to the debug log. The event is USER_DEBUG. The format is timestamp | event identifier:

How to see logs in Apex?

You can view your log in two ways. Before execution, enable Open Log in the Enter Apex Code window. The log opens after your code has been executed. After execution, double-click the log that appears in the Logs tab. Let’s try the first method.

What does it mean when your log level is FINEST?

If your log level is FINEST (2), your code can hit log limits and take longer to run. Don’t worry if you don’t see all the levels when you update the log level for a category. Only the levels that add more logging for the category are listed.

What is the best way to find problems with a program?

Logs are one of the best places to identify problems with a system or program. Using the Developer Console, you can look at various debug logs to understand how your code works and to identify any performance issues.


Leave a Comment