KORE provides many different integrations which automatically copy data into DWA. Unless noted otherwise in a specific integration's documentation, these are our general policies:
Service Level Objective (SLO)
DWA integrations pull data from vendors at least daily, except where noted otherwise. If a refresh fails, it will be noted in our internal daily error report. Most failures are transient or self-correcting but if an integration's refresh fails repeatedly, KORE will investigate it. KORE's objective is to resolve such an outage within one week of the first report, with the exception of outages caused by changes a vendor makes to their server or API—those may need to be added to our development schedule, depending on the scope of the changes.
If your contract with KORE includes an SLA (service level agreement), it takes precedence over this SLO.
Data retention policy
Data is maintained in perpetuity for as long as you are a DWA customer. While the vast majority is in "hot" storage on Amazon S3, in rare circumstances KORE may push data to "cold" storage on Amazon Spectrum. If this happens, the data will remain accessible to you but query performance or functionality may be limited.
See also: KORE Data handling
ERD and data dictionary
When available, an ERD (Entity Relationship Diagram) and/or data dictionary for an integration is provided for convenience. Most of these were not provided by the third party vendor, so they are not guaranteed to be accurate and details could change without notice in the KORE Help Center. We provide these only on a best-effort basis.
DWA uses Amazon Redshift, which does not enforce table constraints. In most cases, these tables do not specify any primary or foreign keys. The "PK" and "FK" notations on our ERDs are inferred and included solely to make the diagrams easier to use. They are not guaranteed to be correct or unique.