Running out of storage space

Actions that you can take if your analytics data is using more persistent storage space than you expected.

Reduce retention period

The simplest remedy to running out of storage space is to reduce the data retention period.

By default, API event records are retained for a maximum number of days. This maximum depends on your deployment profile. To see the default retention settings for each profile, refer to Retention and rollover.

If your analytics subsystem was deployed more recently than your retention period and you are running out of storage space, then there is a risk that your persistent storage fills up before the retention period is reached. For example, if you deployed the n1xc4.m32 profile 15 days ago, and you are already low on storage space, then it is likely you all your storage is consumed before the 30-day retention period for this profile is reached. Check in the Cloud Manager UI how many days back your API event data goes, and set the retention period to a lower number. For example, if you see API event records from 15 days ago, reduce your storage requirement by one-third by setting your retention period to 10 days.

Kubernetes and Openshift users: Reinstall with larger PVCs

It is not possible to increase PVC size after installation. If you require more space for your analytics data, the analytics subsystem must be reinstalled. Follow these steps:
  1. Take a backup of your analytics subsystem: Kubernetes, OpenShift, and Cloud Pak for Integration.
  2. Reinstall your analytics subsystem with a larger PVC size:
  3. Restore your analytics data from your backup: Recovering from a disaster.
Note: If you use a storage class that supports volume expansion, then instead of reinstalling you can attempt to increase the PVC size and then increase the storage volumeSize in the analytics CR. If this is successful then you do not need to reinstall the analytics subsystem.

If you want to try increasing your PVC size, then consult your Kubernetes or Openshift administrator for the steps.

Reduce space used by new API event data

To reduce the storage required for new analytics data, update the activity log settings of your APIs: Activity log policy.
Tip: If you're not able to update the activity log setting for your APIs, you can disable response payload logging for all APIs with ingestion filters. For example: 
filter {
  if "apicapievent" in [tags] {
     mutate {
            remove_field => ["response_body"]
        }
  }
}

What to do if your storage is 100% full

If your storage space is 100% full, your analytics subsystem might be unresponsive, so reducing the retention period is not possible. In this scenario, follow the disaster recovery steps: Recovering from a disaster.