| One or more files generated for every hour of activity. |
One file generated for every 24 hours of activity. |
Available in the API and integrated with the Event Monitoring Analytics app on
request as part of a Beta program. You can manually import data into third-party
visualization apps.As a beta feature, hourly event log file integration with the
Event Monitoring Analytics app is a preview and isn’t part of the “Services” under your
master subscription agreement with Salesforce. Use this feature at your sole discretion,
and make your purchase decisions only on the basis of generally available products and
features. Salesforce doesn’t guarantee general availability of this feature within any
particular time frame or at all, and we can discontinue it at any time. This feature is
for evaluation purposes only, not for production use. It’s offered as is and isn’t
supported, and Salesforce has no liability for any harm or damage arising out of or in
connection with it. All restrictions, Salesforce reservation of rights, obligations
concerning the Services, and terms for related Non-Salesforce Applications and Content
apply equally to your use of this feature. |
Available in the API and integrated with the Event Monitoring Analytics app and
third-party visualization apps. |
Key values in the EventLogFile object are:
-
Interval—Hourly
-
LogDate—Date and hour in which the log file was generated. For
example, for events that occurred between 11:00 AM and 12:00 PM on 3/7/2016, this field’s
value is 2016-03-07T11:00:00.000Z.
To find out when the EventLogFile
object was created, query CreatedDate.
-
Sequence—1+. This value increases by 1 when events are added in
the same hour after the latest event log file is created. The value resets to 1 in the
subsequent hour.
|
Key values in the EventLogFile object are:
-
Interval—Daily
-
LogDate—Date and time of the log file’s creation. For example,
for events that occurred on 3/7/2016, this field’s value is
2016-03-07T00:00:00.000+0000.
-
Sequence—0
|
j