Quota and limits
Quota limits depend on the license agreement and plan.
Quota limits
Reltio enforces quota limits on resource usage for various reasons. For example, quotas protect the community of Reltio Platform users by preventing unforeseen spikes in usage.
Your Quota Limits vary by the license agreement and any pre-paid plans. If you expect a notable upcoming increase in usage, you can proactively request quota increases by reaching out to your Reltio customer success representative.
| Item | Definition | Quota Limit | Request Quota Increase |
|---|---|---|---|
| Reltio Connected Data Platform |
The Reltio base Platform consisting of one Production, one Test, and one Development tenant. |
Contains a Base tenant, and associated Quota Limits, which may vary by License Agreement (See Base tenant) |
N/A |
| Aggregate Consolidated Profile |
A unique profile managed for creating and consolidating data by bringing together attributes from multiple sources |
Varies by limits and types stated in License Agreement. Subscription is limited to profiles for named Data Domain types (the “Permitted Domains”) |
Extra fees for new unique profiles that exceed those previously stated in License Agreement, and/or new Data Domain types to be “mastered” |
| APIs |
Any calls to the Reltio REST API, outside of calls made by the Reltio out-of-the-box User Interfaces (UI). |
1,000,000 per day aggregated across all base platform tenants Maximum processing up to 300 Operations per second (OPS) |
API calls made greater than the maximum per day included in the subscription, will be charged at an extra cost per day |
| Data Domain |
A named domain type, for example: customer, product, organization. Industry-specific examples include HCP or HCO for life sciences. |
Varies by limits and types stated in License Agreement. |
There is a charge for extra data domains |
| Reltio Storage Unit (RSU) |
Total combined primary and secondary storage used across production, test and development tenants, which includes consolidated profiles, reference profiles, interactions, activity log and history data. |
You find the number of RSUs that you’ve contracted for in your order form. You can track your RSU consumption for each tenant on Usage and Billing Metrics page in Console. Note again that your RSU Quotas consumed are the total across all of your tenants. |
Extra fees apply for extension to existing RSU quota limit (see Reltio Quotas). |
Activity log and history data retention periods
Storage occupied by activity logs and history data consumes your allocated Reltio Storage Units (RSUs). To support automatic reclamation of unused data, Reltio supports retention policies for tenant activity logs and history data. Activity log data is collected for all online user actions and API calls made on a tenant. History data contains versions of your entity profiles for each time the entity profile is changed within a tenant.
No matching or merging, merge tree/history, or potential match data is kept in the history dataset. It’s only a snapshot of the entity profile. Enabling retention of entity history records won’t impact matching and merging/unmerging operations.
The retention periods for activity log data and history data are configured per tenant. The same retention period will be used for activity log and history data for a given tenant. This configuration is managed by Reltio.
| Environment Type | Activity Log Retention Period | History Data Retention Period |
|---|---|---|
| Development | 1 month | 1 month |
| Test | 3 months | 3 months |
| Production | 1 to 7 years based on industry type (see table under) | 1 to 7 years based on industry type (see table under) |
You can request custom production retention periods outside of the default values to meet your specific business needs or obligations. Changes to retention periods (up or down) will incur extra costs. In such cases, contact your customer success representative for process and pricing.
The following is the retention period per industry as used by activity log and history data lifecycle management.
| Industry* | Retention Period (Years) |
|---|---|
| Consulting and Business Services | 1 |
| Consumer Packaged Goods | 1 |
| Energy | 1 |
| Finance and Insurance | 6 |
| Healthcare | 7 |
| High Tech | 1 |
| Life Sciences | 7 |
| Logistics and Transportation | 1 |
| Manufacturing | 1 |
| Media and Communications | 1 |
| Retail | 1 |
| Travel and Entertainment | 1 |
| Oil and Gas | 7 |
By default, activity log searches return data for the last four months. If you wish to search beyond the default period of four months, specify the appropriate date/time range.
The table over specifies retention periods for the activity log. Beyond the retention period, all the data is purged. No results are returned for any searches beyond the retention period.
Reltio enforces a monthly quota of 1 TB on queries done on activity log data. To minimize the size of your query and stay within the specified limits, use the appropriate date/time range. The quota is based on the volume of data retrieved from the storage to evaluate queries, and not on the data returned from queries. Queries that exceed this limit aren’t processed.
Activity log notification Alert
- By default, these notifications are sent to the Customer Success Manager. Contact support with a request to change the ownership of these alerts.
- Notifications can be sent to an individual or a group email list.
- Notifications are generated in the following instances:
- When 75% of your quota limit is reached
- Every day after 75% of your quota limit is reached