External OData Callout Event Type

External OData Callout events represent external data callouts via the OData 2.0 and OData 4.0 adapters for Salesforce Connect. This event type is available in the EventLogFile object in API version 40.0 and later.

For details about event monitoring, see the Trailhead Event Monitoring module or REST API Developer Guide.

  • Type: String

  • Description: Action performed by the callout.

  • Possible values:

    • query
    • upsert
    • delete
  • Type: Number
  • Description: Size of the result set in bytes.
  • Type: String
  • Description: Name of the external object being accessed.
  • Example: Order
  • Type: String
  • Description: Type of event. Value is always ExternalODataCallout.
  • Type: Number
  • Description: How long it took (in milliseconds) for Salesforce to prepare and execute the query. Available in API version 42.0 and later.
  • Example: 21
  • Type: String
  • Description: Reserved for future use.
  • Type: Number
  • Description: How long it took (in milliseconds) to retrieve the query results from the external system. Available in API version 42.0 and later.
  • Example: 127
  • Type: Text
  • Description: Field expressions to filter which rows to return. Corresponds to WHERE in SOQL queries and $filter in OData queries.
  • Example: CustomerID eq 12345
  • Type: String
  • Description: Reserved for future use.
  • Type: Number
  • Description: Maximum number of rows to return for a query. Corresponds to LIMIT in SOQL queries and $top in OData queries.
  • Example: 200
  • Type: String
  • Description: Error or warning message associated with the failed call.
  • Example: The OData query result was too large, so the external data didn’t load.
  • Type: String
  • Description: OData next link that the callout used to request a subsequent page of rows. A next link is provided in a previous response from the OData producer when the response includes only part of the result set. Available in API version 42.0 and later. However, this field isn’t supported for the OData 2.0 adapter on orgs created before Spring ’18.
  • Example: http://services.example.org/Warehouse.svc/Orders?$count=true&​$select=CustomerID,OrderID,RequiredDate,ShippedDate&$top=301&​$skiptoken=10447
  • Type: Number
  • Description: Number of rows to skip when paging through a result set. Corresponds to OFFSET in SOQL queries and $skip in OData queries.
  • Example: 10

  • Type: String

  • Description: Field or column to use for sorting query results, and whether to sort the results in ascending (default) or descending order. Corresponds to ORDER BY in SOQL queries and $orderby in OData queries.

  • Examples:

    • ShipName
    • ShipName desc
  • Type: Id
  • Description: 15-character ID of the organization.
  • Example: 00D000000000123
  • Type: String
  • Description: If the callout requested a subsequent page of rows, this field identifies the initial callout whose request resulted in the multipage result set. Available in API version 42.0 and later. However, this field isn’t supported for the OData 2.0 adapter on orgs created before Spring ’18.
  • Example: 4EoZtuBzzRIXSk-ysRdf1F-1

  • Type: String

  • Description: Whether the OData 2.0 or OData 4.0 adapter made the callout.

  • Possible values:

    • OData—OData 2.0 adapter
    • OData4—OData 4.0 adapter
  • Type: Number
  • Description: Consumed percentage of the org’s limit of OData callouts per hour.
  • Example: 2.5—2.5% of the hourly callout limit has been consumed
  • Type: String
  • Description: Unique ID of a transaction. A transaction can contain one or more events. All events in a transaction have the same REQUEST_ID.
  • Example: 4A13-HSKv3CKs-0FKfceaV
  • Type: Number
  • Description: Reserved for future use.
  • Type: Number
  • Description: Total number of records in the result set. Available in API version 42.0 and later.
  • Example: 830
  • Type: Number
  • Description: Number of records fetched by the callout. The records fetched by a callout can be a subset of a large result set. Available in API version 42.0 and later. However, this field isn’t supported for the OData 2.0 adapter on orgs created before Spring ’18.
  • Example: 200

  • Type: String

  • Description: Search query string. Corresponds to condition expressions in SOSL.

  • Example:

  • Type: String
  • Description: Comma-separated list of fields being queried. Corresponds to SELECT in SOQL queries and $select in OData queries.
  • Example: CustomerID,OrderDate,OrderID,ShipCity,ShipCountry

  • Type: Boolean

  • Description: Whether the query was successful.

  • Possible values:

    • 1 - Success
    • 0 - Failed
  • Type: Number
  • Description: Number of records retrieved in one second. Available in API version 42.0 and later. However, this field isn’t supported for the OData 2.0 adapter on orgs created before Spring ’18.
  • Example: 3025.67
  • Type: String
  • Description: The access time of Salesforce services in GMT.
  • Example: 20130715233322.670
  • Type: DateTime
  • Description: The access time of Salesforce services in ISO8601-compatible format (YYYY-MM-DDTHH:MM:SS.sssZ). The timezone is GMT.
  • Example: 2015-07-27T11:32:59.555Z
  • Type: Number
  • Description: How long it took (in milliseconds) to prepare and execute the query and to retrieve the query results.
  • Type: Id
  • Description: 15-character ID of the user accessing the external system.
  • Example: 00530000009M943