Absence of data in the Pods tab or some tabs in the OpenShift monitor

To collect data for the OpenShift Monitor, Applications Manager uses the SSH protocol to connect to the OpenShift server and execute "oc" commands. However, a timeout issue may occur while collecting data if the environment has a large number of pods. We are suggesting two solutions to resolve this issue. To resolve this issue, follow the steps given below:

Solution 1:

Enable Rest API Mode of Monitoring for OpenShift Monitor. This will fix this the timeout issue.

Solution 2:

Use ServerSSHTroubleshoot.bat or sh file from <APM_Home>\bin\troubleshooting to establish an SSH connection with the OpenShift server.
Execute the "oc get pods -o json --all-namespaces" command and calculate the time taken for the command to complete.
Edit the OpenShift Monitor from the Applications Manager GUI.
Update the Timeout value to the time taken for command execution (in seconds).
Update the polling interval to twice the Timeout value (in minutes).

For example, if the command execution time is 300 seconds, update the Timeout value to 300 seconds and the polling interval to 10 minutes.

If the issue persists, send an email to appmanager-support@manageengine.com with a screenshot of the "Edit Monitor" page after clicking on the Test credentials option along with the latest Support Information File (SIF) from Applications Manager with print all logs enabled for analysis.