REST API Developer Guide

Introduction to REST API
Quick Start
Examples
Getting Information About My Organization
Working with Object Metadata
Working with Records
Delete Lightning Experience Event Series
Working with Searches and Queries
Get an Image from a Rich Text Area Field
Insert or Update Blob Data
Get Blob Data
Working with Recently Viewed Information
Managing User Passwords
Working with Approval Processes and Process Rules
Using Event Monitoring
Describe Event Monitoring Using REST
Query Event Monitoring Data with REST
Get Event Monitoring Content from a Record
Download Large Event Log Files Using cURL with REST
Delete Event Monitoring Data
Query or View Hourly Event Log Files
Query Hourly Event Log Files
Differences Between Hourly and 24-Hour Event Logs
Using Composite Resources
Generating an OpenAPI 3.0 Document for sObjects REST API (Beta)
Reference
PDF

Differences Between Hourly and 24-Hour Event Logs

You receive event log files approximately every hour in addition to 24-hour log files. Review the differences between the two logs so that you can filter your files to analyze the event data you want.
Hourly Log Files 24-Hour Log Files
One or more files generated for every hour of activity. One file generated for every 24 hours of activity.
Available in the API. You can manually import data into third-party visualization apps. Available in the API and integrated with the Event Monitoring Analytics app and third-party visualization apps.
Key values in the EventLogFile object for hourly logs. See also these Considerations regarding hourly event logs. Key values in the EventLogFile object for 24-hour logs.
When an hourly incremental log file is delivered, a file with new logs for that hour is created. The Sequence field is incremented for each new file. When a daily incremental log file is delivered, a new file replaces the original file with the full set of available logs for that date. The CreatedDate field is updated.

Key values in the EventLogFile object for hourly logs:

  • Interval—Hourly
  • CreatedDate—Timestamp of when the log file was created. Use this field to identify new files.
  • LogDate—Timestamp that marks the beginning of the interval when the events occurred. 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.
  • 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 for 24-hour logs:

  • Interval—Daily
  • CreatedDate—Timestamp of when the log file was created. Use this field to identify new files.
  • LogDate—Timestamp that marks the beginning of the interval when the events occurred. For example, for events that occurred on 3/7/2016, this field’s value is 2016-03-07T00:00:00.000+0000.
  • Sequence—0

Like with 24-hour event monitoring, hourly event log data is available for the past 30 days.

Note