Easy way to check the Debug logs

Latest Version

Version
1.4.9
Update
December 9, 2024
Size
1.17MiB
Developer
speetus.com
Category
Users
726
Rating
4.66667 ★
Manifest Version
3
Web Store Status
Languages Support
English (United States)
See more
Permissions
ActiveTab
Cookies
Tabs
See more

Salesforce Speedy Debugger Extension

Salesforce Debugger Chrome Extension

Salesforce Debugger Chrome Extension is designed to streamline the debugging process for salesforce developers.This extension offers a comprehensive suite of features aimed at simplifying the management of Trace Flags and Debug Logs within the Salesforce environment. Whether you're troubleshooting code errors, monitoring system behavior, or optimizing performance, this tool provides efficient solutions tailored to your debugging needs.

With intuitive functionalities and seamless integration into your Salesforce workflow, this extension empowers developers to efficiently trace, analyze, and resolve issues, ultimately enhancing productivity and accelerating development cycles. From managing Trace Flags to searching and filtering Debug Logs, this extension equips developers with the tools needed to effectively debug and optimize their Salesforce applications.

In this document, we'll provide a concise overview of the extension's key features, outlining how each functionality enhances the debugging process for Salesforce developers. Whether you're new to debugging in Salesforce or seeking to streamline your current workflow, this extension offers a user-friendly interface and robust capabilities to support your debugging endeavors.

Trace Flag : Functionalities

1.\tAdd Current User (Button):
●\tIf the trace flag for the current user (logged-in user) is not active, prompts to create a new trace flag.
●\tIf the trace flag for the current user is active, displays active records and allows creating a new trace flag by selecting debug level. It replaces the existing trace flag upon saving.

2.\tNew (Button):
●\tCreates a trace flag for a user based on TraceEntityName, StartDate, Expiration Hours, and DebugLevel.
●\tHandles creation for active users, prompts for error on past date selection, and disables save button until debug log is selected.
●\tToast notification on successful creation.

3.\tRefresh (Button):
●\tRefreshes all trace flags.

4.\tDelete (Button):
●\tDeletes the selected record and notifies the user on the scrolled page.
●\tShows error toast if the record is deleted from the org while editing, deleting, or renewing on the extension side.

5.\tRenew (Button):
●\tRenews trace flags for the next 24 hours.
●\tShows error if the trace flag exists for the same traced entity, prompting the user to replace it upon saving.

Debug Log : Functionalities

1.\tUser Search Functionality:
●\tEnables users to search debug logs of active trace flag users.
●\tFilters debug logs using various options, allowing addition and removal of user names.

2.\tSearch String Functionality:
●\tFacilitates searching strings within the debug log body.
●\tHighlights rows containing the searched string, with automatic de-highlighting upon change.
●\tHighlights only the first page of pagination on search.

3.\tAction Tabs:
●\tProvides options to get all logs of the logged-in user, refresh all logs, and delete all logs.

4.\tView (Button):
●\tThe \"View\" button offers a comprehensive insight into various aspects of the debugging process, presenting a series of sub-tabs each with distinct functionalities. Within these tabs:
➢\tLog Details: Users can access creation dates, log lengths, and associated user information.
➢\tDebug Log: This tab displays the debug log body, color-coded to represent different labels for enhanced readability.
➢\tQueries: Developers can review all SOQL queries present in the debug log, including details such as the line number in the Apex class or trigger where the query is written, the number of records retrieved, and the option to navigate directly to the query line within the debug log.
➢\tUser Debug: Custom debug data, such as that generated by system.debug statements, is consolidated in this tab. Users can identify the line number where the debug statement is written, view the printed data, and navigate to the specific debug line within the debug log.
➢\tOrder of Execution: This tab provides insights into debug log limits usage, detailing various limitations such as API call usage or heap size. Users can monitor their usage compared to set limits, with color-coded alerts indicating when usage exceeds 80% (yellow) or reaches 100% (red).
➢\tOrg Limits: Users can access organization-wide limits across different categories presented in a tabular format, facilitating a comprehensive overview of the current usage and thresholds within the Salesforce environment.
➢\tDownload: Users can download debug logs in Excel format with subtabs available on the page.

5.\tDownload (Button):
●\tUsers can download debug logs as well in Excel format.

6.\tDelete (Button):
●\tDeletes the selected record and notifies the user on the scrolled page.

Note: To perform all the activity mentioned above, tool will be used to access the active session id from browser for respective salesforce org.
Read more

Source Manifest.json

{ "update_url": "https://clients2.google.com/service/update2/crx", "manifest_version": 3, "version": "1.4.9", "icons": { "128": "logo.png" }, "name": "Salesforce Speedy Debugger", "description": "Easy way to check the Debug logs", "content_security_policy": {"extension_pages":"script-src 'self'; object-src 'self'"}, "host_permissions": [ "https://*.force.com/*", "https://*.salesforce.com/*", "https://*.develop.my.salesforce.com/*" ], "permissions": [ "activeTab","cookies","tabs" ], "background": { "service_worker": "extension_scripts/background.js" }, "content_scripts": [{ "js": ["extension_scripts/contentScript.js"], "matches": [""], "all_frames":false }], "web_accessible_resources":[ { "resources": [ "src/html/main.html"], "matches": [ "https://*.force.com/*" ,"https://*.salesforce-setup.com/*","https://*.salesforce.com/*", "https://*.develop.my.salesforce.com/*" ] } ] }
Read more