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.
We're currently in the R&D phase of supporting Prometheus mode for OpenShift monitoring. Once it's released, this issue should be resolved.
New to ADSelfService Plus?
Related Articles
OpenShift Monitoring in Rest API Mode
For the OpenShift monitor, data collection when carried out using SSH mode sometimes results in timeout exception due to the presence of large amount of data to be collected. To avoid this, an enhancement has been made and now data collection will ...Absence of data in the Pods tab or some tabs in the Kubernetes monitor
This is a known issue in the older version of Applications Manager, which is fixed in APM v16800. So, we recommend upgrading the Applications Manager to the stable version to properly fix this issue. To collect data for the Kubernetes Monitor, ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...Self monitor Applications Manager using Real User Monitoring
We can monitor the Applications Manager using Real User Monitoring with a Java Script injection and this can be used to measure the Applications Manager's performance continuously. All you need is to install and setup the Real User Monitoring (RUM) ...APM Insight monitor is UP, but monitor page doesn't show any data
Possible Causes The APM Insight monitor status corresponds to the respective agent folder pointed Java Application status i.e., as long as the Application server is running, the monitor status will be UP. 1. No Transactions Recorded: It is possible ...