Many of the system total fields for a target agent are based on the latest known configuration at the latest period of the report window. For example, in the Resource Usage report, # of CPUs, memory size, swap size, CPU utilization and memory utilization take the available capacity at the end of the reporting window as the baseline figure for total capacity. Configuration changes on the system and rescanning of the host in question during the time range included in the report may change these values, even if the collected performance data is unchanged.
This scenario would potentially produce a report of the same data that shows different values depending on the report timeframe. For example:
Configuration Changes Change Detected Change Description 2010-01-27 15:04:43 Memory size changed from 18874368kB to 4194304kB 2010-01-27 11:18:54 Memory size changed from 4194304kB to 18874368kB 2010-01-27 09:15:01 Memory size changed from 18874368kB to 4194304kB 2010-01-27 06:47:17 Memory size changed from 4194304kB to 18874368kB
If we were to run a report on Jan 27 for the system with the above configuration changes, we would see that some reports show memory at 18 Gb, some at 4 Gb and the average as n/a. |
Creating custom reports with Crystal Reports | Rating | Views | |
---|---|---|---|
Use Crystal Reports with up.time's DataStore to generate custom reports. By: uptime Support | Date Created: 11-28-2006 | Last Modified: 7-28-2011 | Index: 103 |
46971 |
Windows process CPU workload stats don't match CPU Total | Rating | Views | |
---|---|---|---|
On multi-cpu or multi-core Windows servers you may notice that the graphing of CPU Total and the graphing of CPU by process (Workload top 10 for example) don't match. For example, you may notice... By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-10-2011 | Index: 245 |
3166 |
Disk and Network stats not recorded on Windows 2008 with Hyper-V | Rating | Views | |
---|---|---|---|
Microsoft introduced a new (V2 performance counters) option to generate performance in Vista/Server 2008. Server 2008 has a problem reporting those counter using the API that the our up.time agent... By: uptime Support | Date Created: 10-2-2009 | Last Modified: 8-13-2011 | Index: 381 |
2312 |
High CPU Usage on Windows Agent | Rating | Views | |
---|---|---|---|
If you observe high CPU usage on systems running the Windows agent, try disabling unused counters (e.g. IIS, SQL, Exchange, etc.) and then restart the agent. If this does not resolve the issue,... By: uptime Support | Date Created: 7-12-2011 | Last Modified: 8-11-2011 | Index: 542 |
3204 |
Using -server option to optimize Java memory usage | Rating | Views | |
---|---|---|---|
Setting the -server Java option will enable the up.time core to use the server JVM, which has enhanced performance and stability for applications that stay running for long periods of time (such as... By: uptime Support | Date Created: 7-12-2011 | Last Modified: 2-1-2013 | Index: 544 |
2963 |