—
Introducing the Global Relay Enterprise Reporting
Service
The Enterprise Reporting Service (ERS) delivers Archive message metadata that your organization can use to build comprehensive compliance reports.
—Why chooseGlobal Relay?
This metadata encompasses the full range of events performed on a message—including basic metadata inherent in all messages, compliance actions, and reviewer workflow events—which provides complete visibility into all compliance events across your entire organization.
Global Relay extracts and delivers message metadata to your organization via the following process:
For the previous 24 hour period, Global Relay extracts metadata for the following:
Newly archived messages
All new events performed on any messages, e.g. reviewed, added to a case, etc.
Legacy imported messages
This metadata is structured into two categories:
Constant metadata: This immutable metadata is constant in all messages (e.g. date, subject, message serial ID, etc.).
Event metadata: Global Relay applies this metadata to a message when an action is performed on it, e.g. a classification tag is applied, a user reviews the message, etc.
The metadata is sent to ERS storage, then reconciled to ensure the completeness of the data.
Note: In the event of a reconciliation discrepancy, data is not exported to the secure SFTP site until the issue is addressed. Typically, reconciliation issues are addressed by the next day, and the data is made available on the SFTP server at that time.
The metadata is transferred to a secure SFTP site, where your organization can download it.
Using the credentials provided by Global Relay, your organization downloads the metadata from the secure, password-protected SFTP site.
Once your organization accesses the SFTP site, the metadata is contained in a folder named after your Global Relay Archive ID.
In this folder, files are organized into date folders (i.e. YYYY-MM-DD). Folders older than 30 days are automatically deleted.
Within each date folder, constant and event metadata are organized into separate zip files. There may be multiple zip files for each type depending on the volume of extracted metadata. Each zip file, which can be up to 2 GB in size, contains files in the Avro format.
Along with the metadata, each date folder contains a manifest file in JSON lines format that includes the file name and size of each metadata file. Each line in the manifest file is a JSON object that provides information about a Zip file that was exported to the SFTP site, as per the following example.
Note: The following example contains a '\' character that identifies the line is continuous:
{"fileName":"8c6a1f32-875d-4a4e-b07c-d3a3970f222f.2025-09-19.events.27494.zip",\"fileChecksum":"8f73361311c88341655273f717badb7fb966cd44c8acf51d0f06626e41ba043c",\"size":10046623}
The fileChecksum value is a SHA-256 hash that can be used to verify the integrity of the metadata file. If the integrity check fails, download the manifest file again to ensure it was downloaded properly during transit..
For more information on the Enterprise Reporting Service, consult the following documentation:
Enterprise Reporting Service Data Dictionary, which provides a detailed explanation of the metadata your organization receives.
Understanding the ERS Data Delivery Schedule Reference Card, which outlines the cadence by which you receive your daily data.
