Enabling Analytics ingestion-only on VMware

Enable the ingestion-only configuration by redeploying the IBM® API Connect Analytics subsystem with the ingestion-only configuration setting.

1. Remove the Analytics service from your API Connect deployment by completing the following steps.
   1. Unassociate the Analytics service from all gateway services as explained in step 7 in the topic, Associating an analytics service with a gateway service.
   2. Unregister the Analytics service from Cloud Manager.

      You can unregister the service from the Topology page: click the Options menu next to the service name and select Delete. For information on registering services, see Registering an analytics service.

2. Create an extra values file to specify the URL of the offload endpoint where all analytics data will be routed.

   You can choose the name for the file, but you must use .yaml as the file-name extension. Format the file as shown in the following example, making sure to include required settings for the third-party system.

   apic-analytics-ingestion:
     outputOffload: |-
         elasticsearch {
           hosts => "http://offload_endpoint:port"
           index => "api-call"
         }
   

   For information about configuring analytics offloading, see Configuring analytics offload for API Connect.

3. Run the following apicup commands to reinstall the Analytics subsystem using the configuration settings in the extra values file:

   apicup subsys set analyt ingestion-only=true
   apicup subsys set analyt extra-values-file=extra-values.yaml
   apicup subsys install analyt

4. Add the new Analytics service to your API Connect deployment by completing the following steps.
   1. Register the new Analytics service with the Cloud Manager.
      Attention: When you register an Analytics service that is configured for ingestion-only, you must use the ingestion endpoint and the ingestion TLS profile instead of the client endpoint and TLS profile.

      For information on registering a service with the Cloud Manager, see Registering an analytics service.

   2. Associate the Analytics service with a gateway service as explained in Associating an analytics service with a gateway service.