Working with Logs in the Developer Console

Debug Log Categories

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

Debug Log Levels

Each debug level includes one of these 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. The level is cumulative, that is, if you select FINE, the log also includes all events logged at the DEBUG, INFO, WARN, and ERROR levels.

• NONE
• ERROR
• WARN
• INFO
• DEBUG
• FINE
• FINER
• FINEST

Debug Event Types

This example shows what is written to the debug log. The event is USER_DEBUG. The format is timestamp | event identifier. This example shows a debug log line.

Debug Log Line Example

• timestamp: Consists of the time when the event occurred and a value between parentheses. The time is in the user’s time zone and in the format HH:mm:ss.SSS. The value in parentheses represents the time elapsed in nanoseconds since the start of the request. The elapsed time value is excluded from logs reviewed in the Developer Console when you use the Execution Log view. However, you can see the elapsed time when you use the Raw Log view. To open the Raw Log view, from the Developer Console’s Logs tab, right-click the name of a log and select Open Raw Log.
• event identifier: Specifies the event that triggered the debug log entry, such as SAVEPOINT_RESET or VALIDATION_RULE.

  Also includes additional information logged with that event, such as the method name or the line and character number where the code was executed. If a line number can’t be located, [EXTERNAL] is logged instead. For example, [EXTERNAL] is logged for built-in Apex classes or code that’s in a managed package.

  For some events, such as CODE_UNIT_STARTED, CODE_UNIT_FINISHED, VF_APEX_CALL_START, VF_APEX_CALL_END, CONSTRUCTOR_ENTRY, and CONSTRUCTOR_EXIT, the end of the event identifier includes a pipe (|) followed by a typeRef for an Apex class or trigger.

  For a trigger, the typeRef begins with the SFDC trigger prefix __sfdc_trigger/. For example, __sfdc_trigger/YourTriggerName or __sfdc_trigger/YourNamespace/YourTriggerName.

  For a class, the typeRef uses the format YourClass, YourClass$YourInnerClass, or YourNamespace/YourClass$YourInnerClass.

In this example, the event identifier consists of:

• Event name:
  1USER_DEBUG

• Line number of the event in the code:
  1[2]

• Logging level the System.Debug method was set to:
  1DEBUG

• User-supplied string for the System.Debug method:
  1Hello world!

This code snippet triggers this example log line.

Debug Log Line Code Snippet

115:51:01.071 (55856000)|DML_BEGIN|[5]|Op:Insert|Type:Invoice_Statement__c|Rows:1

In this example, the event identifier consists of:

• Event name:
  1DML_BEGIN

• Line number of the event in the code:
  1[5]

• DML operation type—Insert:
  1Op:Insert

• Object name:
  1Type:Invoice_Statement__c

• Number of rows passed into the DML operation:
  1Rows:1

These event types are logged. The table lists which fields or other information are logged with each event, and which combination of log level and category causes an event to be logged.

1SOQL queries
2SOQL query rows
3SOSL queries
4DML statements
5DML rows
6CPU time in ms
7Heap size in bytes
8Callouts
9Email invocations
10Future calls
11Jobs in queue
12Push notifications

1SOQL queries
2SOQL query rows
3SOSL queries
4DML statements
5DML rows
6CPU time in ms
7Heap size in bytes
8Callouts
9Email invocations
10Future calls
11Jobs in queue
12Push notifications

1SOQL queries
2SOQL query rows
3SOSL queries
4DML statements
5DML rows
6CPU time in ms
7Heap size in bytes
8Callouts
9Email invocations
10Future calls
11Jobs in queue
12Push notifications

1SOQL queries
2SOQL query rows
3SOSL queries
4DML statements
5DML rows
6CPU time in ms
7Heap size in bytes
8Callouts
9Email invocations
10Future calls
11Jobs in queue
12Push notifications

1Number of SOQL queries
2
3Number of query rows
4
5Number of SOSL queries
6
7Number of DML statements
8
9Number of DML rows
10
11Number of code statements
12
13Maximum heap size
14
15Number of callouts
16
17Number of Email Invocations
18
19Number of fields describes
20
21Number of record type describes
22
23Number of child relationships
24
25 describes
26
27Number of picklist describes
28
29Number of future calls
30
31Number of find similar calls
32
33Number of System.runAs() 
34
35invocations

1var1:50
2
3var2:'Hello World'

1var1:50
2
3var2:'Hello World'