Date: Thu, 28 Mar 2024 21:48:15 +0000 (UTC) Message-ID: <1479032713.5511.1711662495731@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5510_789817220.1711662495727" ------=_Part_5510_789817220.1711662495727 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This article explains how to interpret and address the condition= that causes the Performance Monitor to return the following message:
Limited performance data available, no check com= pleted. |
---|
Details
This message indicates that, at the time the service monitor was run, no= performance data was collected from the agent within the "Sustained Averag= e Time Interval". An accurate check could not be run because there was no d= ata against which to perform a check.
The Performance monitor relies on the performance data that is collected= by the Platform Performance Gatherer. If the Performance monitor runs more= frequently, or checks too little performance data, the monitor may find th= at there is no performance data to check against.
An example of circumstances that may cause this message to appear follow= s:
In the example above, the Performance monitor will run twice before the = Platform Performance Gatherer collects new data from the agent. This happen= s because the Performance monitor only looks at the past minute of historic= al CPU performance data to determine the status of the monitor. The monitor= is likely to miss any older data that was collected by the Platform Perfor= mance Gatherer.
Another example involves checking CPU usage for a specific process. By d= efault, the Uptime Infrastructure Monitor agent collects information about = the top 20 processes (based on CPU load) on the system that is being monito= red. If the process that you want to check for CPU usage does not fall into= the top 20 processes, the Performance monitor will not be able to verify t= he performance of the process. Instead, it will return the Limited performa= nce data available, no check completed message.
Solution
Ensure that the Sustained Average Time Interval is greater than the chec= k interval for the Platform Performance Gatherer for the agent against whic= h the service is running. This enables the agent to collect data more often= than the Performance monitor checks it and ensures that the Performance mo= nitor always has data from the agent to check against.
For example, change the Sustained Average Time Interval so that:
In this case, the Performance monitor runs once every five minutes, will= check data from the last 10 minutes and therefore should always find good = data.
As another example, change the check interval for the Platform Performan= ce Gatherer so that:
In this case, the performance data from the agent is updated once per mi= nute and the Performance monitor should always have some data to check agai= nst, even if the monitor only looks for one minute of data.