IBM Support

Troubleshooting API Connect Analytics - No analytics are seen in the APIC analytics dashboard.

Troubleshooting


Problem

Troubleshooting API Connect Analytics - No analytics are seen in the APIC analytics dashboard.

Symptom

Missing analytics

Cause

This could be caused by multiple reasons as outlined below.

Resolving The Problem

Check the logs of mtls-gw pod for any _bulk request coming from gateway:

     oc logs analyt-mtls-gw-7665f5d445-4cx4n -n <namespace>

10.254.6.1 - - [22/Sep/2021:18:05:54 +0000] "POST /x2020/v1/apievent/_bulk HTTP/1.1" 200 2 "-""-" 2841 0.072 0.070

If you see these requests, we know that wsm-agent running on the DataPower Gateway is sending the requests to analytics server.

If there are no _bulk requests, then the problem is with the gateway and wsm-agent which is not sending bulk requests to analytics server.

If _bulk requests are processed successfully you will see a return code 200, indicating the bulk request has been ingested.

If it is any other return code, check the ingestion pod logs for any errors, which will indicate any issues during ingestion:

    oc logs analyt-ingestion-78d7cff7f7-6pktd

If everything with the data flow looks fine and if you are unable to see analytics, then check the health of analytics by executing into one of the storage pods:

     oc exec -it <storage pod> — bash

       bash-4.4$ curl_es  _cluster/health?pretty=1

Ex:

       bash-4.4$ curl_es _cluster/health?pretty=1

{

  "cluster_name" : "apic-analytics-cluster",

  "status": "yellow",

  "timed_out": false,

  "number_of_nodes": 3,

  "number_of_data_nodes": 1,

  "active_primary_shards": 258,

  "active_shards": 258,

  "relocating_shards": 0,

  "initializing_shards": 0,

  "unassigned_shards": 510,

  "delayed_unassigned_shards": 0,

  "number_of_pending_tasks": 0,

  "number_of_in_flight_fetch": 0,

  "task_max_waiting_in_queue_millis": 0,

  "active_shards_percent_as_number": 33.59375

}

Check the status of the cluster (red, yellow, green)

Green indicates all indices are fine.

Yellow indicates there are some unassigned shards, which may still be replicating.

Red indicates there is a problem with one or more of the indices.

Get a list of all indices using:

bash-4.4$ curl_es  _cat/indices?v

Find the red indices and delete them using:

bash-4.4$ curl_es -XDELETE <index_name>

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"ARM Category":[{"code":"a8m50000000CeBlAAK","label":"API Connect->Management and Monitoring (MM)->Analytics"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0.0;2018.4.1.0"}]

Document Information

Modified date:
18 October 2021

UID

ibm16494953