Transactions Data Export
The Transaction Monitoring Observability API now supports on-demand Transactions Data Export, enabling users to request and retrieve a report of transaction IDs ingested on a specific date. This provides a structured mechanism to reconcile which transactions have been received by Transaction Monitoring for a given day.
Exports return transaction identifiers (modification IDs) only for the requested date.
Exports are generated asynchronously:
- Trigger a report for a chosen date and receive a
trigger_id - Use the
trigger_idto retrieve the report once it is ready
Note: This export is not a substitute for alert data sources.
Key Capabilities
-
Trigger export generation for a specific date via:
POST /api/v1/data-export/trigger
→ Returns atrigger_id -
Retrieve the export report via:
GET /api/v1/data-export/{trigger_id}
→ Available once processing is complete -
Poll the retrieval endpoint using the
trigger_idto check readiness -
Download the exported file via a time-limited URL
→ Valid for 15 minutes from issuance -
Access export data and associated metadata for up to 30 days (tenant-configurable), aligned with Observability API retention policies
Report Contents
The export includes:
- Transaction modification IDs only for the requested date
The export does not include:
- Full transaction payloads
- Alert data
- Alert-to-transaction relationships
- Rule execution details
Prerequisites
- Export files must be downloaded within the 15-minute URL validity window
- If the URL expires, a new retrieval request is required to obtain a fresh download link
Recommended Practice: Periodic Download & Archival
To maintain long-term transaction reconciliation records for compliance, audit, and operational workflows, we recommend establishing a regular download schedule—for example, weekly—and archiving reports to your own systems. Once downloaded, you own the data and can retain it as long as your requirements dictate, independent of the Observability API data retention policies.