| Skip Navigation Links | |
| Exit Print View | |
|
Oracle® ZFS Storage Appliance Analytics Guide |
By default, the appliance indefinitely retains analytical data for all active datasets on a per-second basis. Since this could consume large amounts of disk space and create large datasets that are slow to manipulate in the BUI, it is strongly recommended that you set data retention policies. Retention policies are especially important if you plan to retain large amounts of historical data for an extended period.
A retention policy limits the minimum amount of data collected by a data fidelity level of per-second, per-minute, or per-hour over a period of time, or retention period. You could set one retention policy per data fidelity level. For example, you could define a retention policy to save a minimum of one day of data at the per-second interval, a second policy to save a minimum of one week of data at the per-minute interval, and a third policy to save a minimum of one month of data at the per-hour interval. It is recommended that you only keep the minimum amount of data according to your business requirements, including compliance needs.
Per-second data is the highest fidelity and requires more memory and disk space than per-minute or per-hour data. Likewise, setting a longer retention period corresponds to storing more data. Monitor the size of the datasets in the BUI by navigating to Analytics -> Datasets, and in the CLI by using the analytics datasets context. Adjust retention policies accordingly to meet business requirements while occupying the least amount of space. Retention policies apply to all active datasets; suspended datasets are not affected.
Note that you must increase the retention time with each retention fidelity increase. For example, you cannot define a retention period of weeks for per-second data and then define a retention period of days for per-minute data.
Worksheet graphs are displayed in the highest data fidelity available to the appliance. For example, if your retention policies do not collect per-second data but do collect per-minute data, the graphs are rendered using per-minute data.
When you enable a data retention policy, you should assume that old data is immediately removed. For example, if you set a per-second policy for at least three hours, you should assume that any data over three hours old is deleted. In actuality, the appliance periodically deletes old data and may delay removing old data to avoid causing a performance impact. You can significantly reduce the space used by Analytics by setting a retention policy that periodically discards the highest fidelity data.
To enable a retention policy, you must have Super-User privileges or have configure authorization within the Dataset scope. See the Chapter 7, User Configuration, in Oracle ZFS Storage Appliance Administration Guide for more information on defining authorization scopes for users.
For each of the properties below you either select "All" or "At least". If you select "All" you are not defining a retention policy for the data retention interval and the appliance will not limit active datasets. If you select "At least", enter an integer value into the text box. Then select the period for the retention policy: hours, days, weeks or months. These settings apply to all active datasets and should be set according to business requirements, including compliance needs.
|
|