This issue can have multiple causes and resolutions. These will be marked in the vCenter Storage and Collection Routine for WCP events (Kubernetes) sections.
/storage/core/loginsight/var/plugins/vsphere/li-vsphere.log
file you may see entries similar to:2020-05-11 19:25:16.167+0000] ["pool-11-thread-1"/[IP of vCenter] ERROR] [com.vmware.loginsight.scheduled.ScheduledPluginService] [Error running vSphere WCP collection]
java.lang.Exception: vCenter API vcenter.example.com is not available, response code: 403, message: {"type":"com.vmware.vapi.std.errors.unauthorized","value":{"messages":[{"args":[],"default_message":"Unable to authorize user","id":"vapi.security.authorization.invalid"}]}}
[2020-04-24 06:32:51.740+0000] ["ScheduledPluginServiceScheduledTask-thread-1"/##.##.##.## ERROR] [com.vmware.loginsight.scheduled.ScheduledPluginService] [Timeout on waiting '##.##.##.##
', timeo
ut=600000 millis. vCenter can't complete requested range in time. Increasing vsphere's config event-collection-timeout-millis may mitigate the problem but that may introduce delays to other vCenter collectors.]
java.util.concurrent.CancellationException
To resolve this issue, follow Delete old tasks, events and statistics data in vCenter Server 5.x, 6.x, 7.x and 8.x and set all of the parameters to 0.
Do not interrupt the script until complete.
You can disable the collection of these events and prevent the error by following the steps below:
/usr/lib/loginsight/application/etc/loginsight-config-base.xml
wcp-collection-enabled
to false. <wcp-collection-enabled value="false" />
service loginsight restart
6. Repeat steps 2-5 to each Aria Operations for Logs node as needed.