Salesforce Advance Administrator Notes (Auditing & Monitoring)
Auditing & Monitoring
Auditing features do not secure your organization by themselves, but these features provide information about usage of the system, which can be critical in diagnosing potential or real security issues. Auditing features include:
- Record Modification Fields (Owner, Created By, Modified By, Last Modified Date, Created Date)
- Login History ( 6 Months History. 20,000 recent Logins)
- Field History Tracking (Accounts, Cases, Contacts, Entitlements, Service contracts, Contract line items, Contracts, Leads, Opportunities, Articles, Solutions)
- Setup Audit Trail (180 Days, 20 Most recent changes, Changes of Administration , Customization , Security & Sharing , Data Management , Development , Various Setup , Using the Application is tracked )
- Dreamfactory Snapshot (Compare and diff Orgs, Analyze changes to Orgs, and push customizations between Orgs, all with no coding required)
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
- Resources used by Apex
- Automated workflow processes, such as:
- Workflow rules
- Assignment rules
- Approval processes
- Validation rules
The system generates a debug log every time a transaction that is included in the defined filter criteria is executed.
Transactions can be generated from the following:
- Salesforce user interface
- Web services
- Email services
Debug logs don’t include transactions that are triggered by lead conversion. For example, suppose a converted lead triggers a workflow rule. The debug log won’t show that this workflow rule fired.
Debug Log Limits
The following are the limits for debug logs:
- Once a user is added, that user can record up to 20 debug logs. After a user reaches this limit, debug logs stop being recorded for that user. ClickReset on the Monitoring Debug logs page to reset the number of logs for that user back to 20. Any existing logs are not overwritten.
- Each debug log can only be2 MB. Debug logs that are larger than 2 MB are reduced in size by removing older log lines, such as log lines for earlier debug statements. The log lines can be removed from any location, not just the start of the debug log.
- Each organization can retain up to50 MB of debug logs. Once your organization has reached 50 MB of debug logs, the oldest debug logs start being overwritten.
- The newest log entries are always preserved. The debug log is truncated by200 KBytes when it reaches its maximum size of 2 MB.