Changing performance data expiration times 

Performance data stored in OpsCenter expires after configurable time periods.

cluster_name.conf 

The location of the cluster_name.conf file depends on the type of installation:

  • Package installations: /etc/opscenter/clusters/cluster_name.conf
  • Tarball installations: install_location/conf/clusters/cluster_name.conf

Performance data stored in OpsCenter expires after configurable time periods. The default values are designed to provide efficient compaction and eventual deletion of the data, with faster expiration times for the more granular, larger-volume data roll-ups.

  • One-minute roll-ups (1min_ttl) expire after one week, or 604800 seconds.
  • Five-minute roll-ups (5min_ttl) expire after four weeks, or 2419200 seconds.
  • Two-hour roll-ups (2hr_ttl) expire after one year, or 31536000 seconds.

To change expiration time period:

In this example, the one-minute and five-minute roll-ups are set to expire twice as fast as the defaults, two-hour roll-ups are set to be kept indefinitely (expiration is disabled), and the 24 hour roll-ups are not going to be stored.

Procedure

  1. Edit the cluster_name.conf file.
  2. Add the following time-to-live (ttl) values in seconds under a [cassandra_metrics] section:
    
    [cassandra_metrics]
    
    1min_ttl = 302400
    5min_ttl = 1209600
    2hr_ttl = 0
    24hr_ttl = -1
    
  3. Restart OpsCenter.
    Data collected after restarting OpsCenter expires according to the new settings. The data collected before restarting OpsCenter expires according to the setting in effect when it was collected.