Given a scenario, determine the appropriate tools for monitoring and troubleshooting system activity.
Salesforce provides several tools to debug system and user activities. To identify and issue, the order in which Salesforce executes activities needs to be considered.
Several tools exist to debug and troubleshoot activities in Salesforce.
|Setup Audit Trail||Configuration changes by Salesforce administrators.|
|Debug Logs||System activities and transactions.|
|Email Logs||Emails sent from within Salesforce.|
|Login History||Login attempts to Salesforce.|
The Setup Audit Trail logs all configuration changes performed by System or Delegated Administrators. It provides information about each change, such as date/time, user, and which component was changed in what way.
The 20 last entries can be access within Salesforce. A full list of all configuration changes performed within the last 6 months can be downloaded as a CSV file.
Debug Logs track system events and transactions in Salesforce. They contain information about:
Debug Logs are generated when attached to users using Trace Flags, when Apex tests are run, and when Apex or API requests contain debug statements or headers. The level of detail included in Debug Logs can be defined with Log Levels.
Trace Flags can be attached to individual users, to record Debug Logs for those users.
Debug Levels define the level of detail included in Debug Logs.
Each Debug Log entry is limited to a size of 5 MB. After this, log entries are removed starting with the oldest entries. Furthermore, only 250 MB of Debug Logs can be generated within 15 minutes. After this, active Trace Flag get deactivated. They can be reactivated again after 15 minutes and after deleting old Debug Log entries.
Email Logs contain information about all emails sent through Salesforce. They provide details about email sends, such as sender and recipient email addresses and deliverability status.
Email Logs need to be requested and can be downloaded as a CSV file after its on demand generation. They only contain data about email sends from the last 30 days, and are limited to 500'000 records.
The Login History shows information about login attempts to the Salesforce org. It provides details such as login user, time, IP, location, type, and success.
The Login History page contains data about login attempts from the last 60 days, and is limited to 20'000 records. To access more records, the Login History can be downloaded as a CSV or GZIP file.
When a user saves a record in Salesforce, system activities are processed in a predefined order before the record is committed to the database.