--- schema_version: "1" id: 78c0bdfb88094fd6af961d1941f1d39f82eb453cc801a6c439411040036040b5 title: Logs Tab collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/code_dev_console_tab_browser_logs.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.code_dev_console_tab_browser_logs.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 6cfe6b15dbcf61bb93200e42a07713ace17b158fc22ee70f775f9d1fb455fe01 description: Use the Logs tab in the Developer Console to access logs that include database events, Apex processing, workflow, callouts, and validation logic. products: - Salesforce Platform release: "264" --- # Logs Tab Use the Logs tab in the Developer Console to access logs that include database events, Apex processing, workflow, callouts, and validation logic. The Developer Console automatically polls for the current user’s debug logs and lists them on the Logs tab. For example, if you have validation rules associated with inserting a record and you insert a new record, the Developer Console captures a debug log for the request and adds it to the list. ![Use the Logs tab to open relevant debug logs for review](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_code-264-0-0-production-enus/789bc523-706b-4ae4-8fe9-be6322e38b6b/extend_code/images/code_dev_console_browser_logs_controls.png) - To open the selected log in the Log Inspector, select **File** | **Open Log** or double-click the log on the Logs tab. Use the Log Inspector to review a debug log, evaluate Apex code, track DML, monitor performance, and more. - To open the selected log in a text editor, select **File** | **Open Raw Log**. Or, right-click a log on the Logs tab and select **Open Raw Log**. String values that are truncated to 512 characters in the Log Inspector aren’t truncated in raw logs. - To filter the visible logs, click **Filter** and type the text you want included in the list. For example, if you want to see debug logs from a specific user, type that user's name. The filter is case-sensitive. - To remove all logs from the list, click **Debug** | **Clear** | **Log Panel**. - By default, the **Logs** tab displays only new logs generated by the current user. To see all debug logs saved for your organization, including newly generated logs created by other users, click **Debug** and deselect **Show My Current Logs Only**. - To automatically hide all existing logs the next time the page is refreshed, click **Debug** and select **Auto-Hide Logs**. - To download a copy of the selected log as a text file, click **File** | **Download Log**. The default name for the file is apex.log. - To prevent logs from loading when you open the Developer Console, go to **Help** | **Preferences** and set **Prevent Logs on Load** to true. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_code-264-0-0-production-enus/789bc523-706b-4ae4-8fe9-be6322e38b6b/images/icon_note.png) Note User logs are configured from the Debug Log page in your org. From Setup, enter Debug Logs in the Quick Find box, then select **Debug Logs**. ## Setting Logging Levels Logging levels determine how much request information is saved in a debug log. Parsing a large log can take a long time. To reduce the size of a log, adjust the logging level. Use verbose logging for code you’re reviewing. Use terse logging for code you’re not interested in. To specify logging levels for future requests, click **Debug** | **Change Log Levels**. This page allows you to define trace flags and debug levels. To override the default log levels for a specific class or trigger, or to set up logging for a user, add a trace flag that includes a duration and a debug level. To save your changes and close the window, click **Done**. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_code-264-0-0-production-enus/789bc523-706b-4ae4-8fe9-be6322e38b6b/images/icon_note.png) Note If you are debugging using checkpoints, set the Apex Code logging level to FINER or FINEST. (Do not use FINEST for deployment.) ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_code-264-0-0-production-enus/789bc523-706b-4ae4-8fe9-be6322e38b6b/images/icon_important.png) Important If the Developer Console is open, the general log levels defined in the Developer Console affect all logs, including logs created during a deployment. Before running a deployment, verify that the Apex Code log level is not set to Finest, or the deployment might take longer than expected. #### See Also - [Debug Logs](https://help.salesforce.com/s/articleView?id=platform.code_debug_log.htm&release=264.0.0&type=5 "Use debug logs to track events that occur in your org. Debug logs are generated when you have active user-based trace flags, when you run Apex tests, and when executed code or API requests include debugging parameters or headers.") - [Set Up Debug Logging](https://help.salesforce.com/s/articleView?id=xcloud.code_add_users_debug_log.htm&type=5&language=en_US) - [Developer Console Debug Menu](https://help.salesforce.com/s/articleView?id=platform.code_dev_console_menu_debug.htm&release=264.0.0&type=5 "The Developer Console Debug menu allows you to manage your logs and execute anonymous Apex. It includes these options.") - [Log Inspector](https://help.salesforce.com/s/articleView?id=platform.code_dev_console_view_system_log.htm&release=264.0.0&type=5 "The Log Inspector is a context-sensitive execution viewer in the Developer Console. It shows the source of an operation, what triggered the operation, and what occurred next. Use this tool to inspect debug logs that include database events, Apex processing, workflow, and validation logic.") - [Debug Log Levels](https://help.salesforce.com/s/articleView?id=platform.code_setting_debug_log_levels.htm&release=264.0.0&type=5 "To specify the level of information that gets included in debug logs, set up trace flags and debug levels. The debug levels assigned to your trace flags control the type and amount of information that is logged for different events. After logging has occurred, inspect debug events in your debug logs.") - [Debug Log Order of Precedence](https://help.salesforce.com/s/articleView?id=platform.code_debug_log_precedence.htm&release=264.0.0&type=5 "Which events are logged depends on various factors. These factors include your trace flags, the default logging levels, your API header, user-based system log enablement, and the log levels set by your entry points.")