Event Monitoring

Transaction Security email notifications contain more trigger event detail. Append only new data to Event Monitoring Analytics app datasets for more efficient daily dataset updates (beta). New event log file types help you analyze flow trends, monitor CORS violation records, audit installed managed packages that use named credentials, and monitor Bulk API 2.0 usage and performance.

  • Append New Data to Event Monitoring Analytics App Datasets (Beta)
    Now you can configure your app to add only the data that’s new since the last dataset update. This change reduces network loads, can speed up dataflow jobs for large datasets, and helps you stay within your limits. No more worrying about updates leading to duplicated data across multiple datasets and counting against your row count limits.
  • Get More Informative Transaction Security Policy Notifications
    Email notifications for triggered Transaction Security policies include more detail. In addition to the policy name and events that triggered the policy, you now see the policy’s ID and related org ID and user ID. More information helps you identify affected orgs and streamline investigations.
  • Analyze Your Flows in the Flow Execution Event Type
    To analyze the usage trends and performance health of your flows, access the new Flow Execution event type in the EventLogFile object.
  • Get Information About CORS Violation Records in the EventLogFile
    The new CORS Violation Record event type in the EventLogFile object captures information about Cross-Origin Resource Sharing (CORS) violations for Lightning apps. Cross-origin requests to Lightning apps are blocked unless the request comes from a URL listed in your CORS allowlist. Use this event type to monitor CORS violation records and help you decide if your CORS allowlist requires an update before the Enforce CORS Allowlist for Lightning Apps release update is enforced. Currently, the CORS allowlist in Setup isn’t enforced for Lightning apps.
  • Get the Namespace of Installed Managed Packages That Access Named Credentials
    Capture information about Apex callouts that use named credentials as their endpoints with the EventLogFile object’s new Named Credential event type. This event type is ideal for auditing the installed managed packages that use named credentials. For example, you’re sometimes required to create a named credential as part of the installation of a managed package from an AppExchange partner. However, in previous Salesforce releases, you didn’t have a way to determine whether other packages also used the named credential, which was a potential security risk. This new event type allows you to track all packages that use a named credential and investigate packages you don’t recognize.
  • Review Bulk API 2.0 Workload Information
    The new Bulk API 2.0 event log file type helps you query Bulk API 2.0 job information. Previously, Bulk API 2.0 information was available only on the Bulk Data Load Jobs page in Setup. Use the new event type to track how long Bulk API 2 jobs take to complete, what kinds of data they process and how much, who runs jobs, and more.
  • Review Threat Detection Data in Security Center (Generally Available)
    Now generally available, Threat Detection integration with Security Center helps you understand threat event trends and plan your responses accordingly. You can view aggregated data about threat events for single and multiple orgs, and drill in to event details right from the Security Center app.

Event Monitoring (salesforce.com)