Disable local storage

If you are offloading you API event data to a third-party system, you can disable local storage to reduce subsystem resource requirements.

The analytics subsystem provides a complete solution for routing, storing, and viewing the analytics data. However, you might not need the internal storage and viewing solution if you are using a third-party system for data offloading. In this scenario, you can greatly reduce your CPU and memory costs by disabling the internal storage and viewing components.

Important:

If you disable local storage, the analytics views in your API Connect UIs remain accessible, but are empty.

Configure local storage disablement before installation. It is not possible to disable or re-enable internal storage after installation.

You can enable offload of analytics data to third-party systems after installation.

Disabling local storage on Kubernetes, Red Hat OpenShift and Cloud Pak for Integration

When you disable internal storage for analytics data, the following microservices are disabled:
  • osinit
  • storage
During the API Connect installation process, set storage.enabled to false in the CR:
storage:
  enabled: false
The relevant installation pages for each platform are: