REST API Developer Guide

Introducing Lightning Platform REST API
Quick Start
Examples
Getting Information About My Organization
Working with Object Metadata
Working with Records
Working with Searches and Queries
Insert or Update 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
Generate Hourly Event Log Files (Beta)
Query Hourly Event Log Files
Differences Between Hourly and 24-Hour Event Monitoring
Using Composite Resources
Reference
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Differences Between Hourly and 24-Hour Event Monitoring

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 and integrated with the Event Monitoring Analytics app on request. 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 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.

    Tip

  • 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
Latent log files cause a new log file for a particular event or hour to be created, containing only new event logs for that event or hour. Latent log files cause a new log file for a particular event or date to be created, containing all event logs for that event or date.

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

Note