Configuring analytics offload for API Connect

The event data that is generated and collected in your API Connect on-premises cloud can be forwarded to different destination targets for display and analysis. Destination targets include the API Connect user interfaces, and third-party systems that are external to API Connect.

About this task

API event data can be forwarded to a third-party system for data consolidation within data warehouse systems, enhanced monitoring, and richer analytical data processing. The data offload capability in API Connect enables users to form correlations with other data sources on a single platform, and helps to reduce the time between analysis, decision, and action. When you offload event data to a third party system, the data is streamed in real time to the target system as the events occur. Multiple target systems are supported for the data offload.

You can configure a combination of destination systems to which data is forwarded for analysis and display. You can choose one of the following options:
  • Enable access to analytics data in the API Manager user interface. This is the default setting.
  • Disable access to analytics data in API Connect and instead re-route the data streams to one or more third-party systems. When you select this method, the data is not written to the API Connect analytics management server.
  • Enable access to analytics data in API Connect and simultaneously stream the data to one or more third-party systems.
  • Enable the Analytics Message Queue. The Analytics Message Queue acts as a broker between the ingestion pipelines to ensure data collection continued uninterrupted if the offline endpoint becomes nonfunctional. See
  • Completely disable access to analytics data.

Use the following information to configure destination targets for your analytics data: