Track External Object Data Callouts with Event Log Files (Pilot)
We added event types to the
EventLogFile standard object to track Salesforce Connect callouts to external systems. Now you can audit the historical activity of your org’s access
to external object data. For each callout, you can check whether it was a query or write
operation, when the call occurred, and which user accessed the external data. These events are
available in the API, but not yet in the Event Monitoring Analytics app.
We’ve added three event types to the EventLogFile object.
- External Cross-Org Callout—Callouts made via the cross-org adapter for Salesforce Connect
- External Custom Apex Callout—Callouts made via custom adapters for Salesforce Connect
- External OData Callout—Callouts made via the OData 2.0 and OData 4.0 adapters for Salesforce Connect
Example
Suppose that your Salesforce org connects to an external system via an OData adapter.
When you defined the external data source in Salesforce, you selected Named
Principal for Identity Type. With the named principal, the same set of credentials is always used to access
the external system from your org.
To identify the users who accessed an external object’s records during a specific time period, use the log data for the External OData Callout event type. Sort by ENTITY and USER_ID to see which users accessed the external object.
In this event log
file, we see that the Product external object was accessed by three users over 12
callouts.