Acoustic Exchange has a limited retention policy for event data.
There are multiple system behaviors depending on the data exchange scenario chosen by a user. For users that leverage event syndication, an endpoint can be classified as either a pull destination endpoint or a push destination endpoint. For event pull endpoints, Exchange writes and stores events as data files. In this scenario, Exchange users use an external API to pull or download event files into their system environment. These files are available for only three days.
For event push consumers, Acoustic Exchange will deliver events by calling a destination endpoint in real-time. If this destination is unavailable due to an outage, Exchange will attempt one retry call to the destination endpoint. If the destination is still unavailable, Exchange will write and store events as data files. In this scenario, Exchange users must use an external API to pull or download event files into their system environment. These files are available for only three days.
Under special circumstances, Acoustic Exchange can be configured to extend the retention period on a client by client basis. Clients that require a retention period longer than three days must contact Acoustic Exchange Support with a request and business justification. For users who want greater data retention control, there are multiple pre-integrated cloud storage endpoints that can be used to send events to those destinations.
Note, that data exchanges to these types of endpoints are subject to the data syndication volume limits applicable to non-Acoustic endpoints.
Please sign in to leave a comment.