Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following reports enable you to visualize the overall performance of a system in the up.time environment, as well as analyze the information to determine the cause of problems with those systems:

Resource Usage Report

The Resource Usage report tracks the usage of system resources and performance information for systems over a given period of time. In addition to the usage information reported on, the report displays the following information:

  • the name and description of the system
  • an overview of the system configuration, including architecture, memory size, operating system version, number of CPUs, and host ID

Creating a Resource Usage Report

To create a Resource Usage report, do the following:
  1. In the Reports Tree panel, click Resource Usage.
  2. In the Date and Time Range area, select the dates and times on which to report.  For more information, see Understanding Dates and Times.
  3. Select one or more of the following report options:
    • Resource Utilization
      The average and maximum amount of CPU and memory use.

    • CPU Performance Graph
      Tracks the performance of a system’s CPU over a specified time period. This information appears as a graph in the report.

    • Multi-CPU
      The percentage of total CPU time used on systems with more than one CPU.

      Info

      If you find the report’s rendered graph too dense due to a large number of CPUs, alternatively generate a Multi-CPU Usage graph while including fewer CPUs.

    • Network I/O
      The average amount of traffic, measured in megabytes per second, that is traveling through the network interfaces. The report also identifies bursts in network activity that may occur over short intervals. This information appears as a graph in the report.
    • Network Errors
      Any errors that have occurred with the physical network interface. The errors can be, for example, collisions or handshake errors between a system and a switch.
    • TCP Retransmits
      Any network services that may not be completing properly because of undue network or system load. This information appears as a graph in the report.
    • Free Memory
      The amount of free memory available to the system. This information appears as a graph in the report.
    • Page Scanning Statistics
      The number of file system pages scanned by the page scanning daemon. This information appears as a graph in the report.
    • Disk Statistics
      The following statistics for each disk on a system:
      • percentage of the disk that is busy
      • average queue length
      • number of reads and writes per second
      • number of blocks accessed per second
      • average wait time, in seconds
      • average service time, in seconds
      Info

      If the system for which you are creating a report for has multiple disks, a graph for each disk on the system is generated.

    • File System Capacity
      The amount of free disk space on the system. This information appears as a graph in the report.
    • Workload (Top 10 - CPU)
      The top 10 processes that are consuming CPU time, grouped by user ID, group ID, and process name. This information appears as a graph in the report.

      Info

      This graph does not appear when you generate this report for a VMware ESX system.

    • Workload (Top 10 - Memsize)
      The top 10 processes that consume system memory, based on the total memory size of the processes - including virtual pages and shared memory. This information appears as a graph in the report.

      Info

      This graph does not appear when you generate this report for a VMware ESX system.

    • Workload (Top 10 - RSS)
      The top 10 processes that are consuming physical memory (in KB), as measured by the run-set size (RSS) of the process. This information appears as a graph in the report.

      Info

      This graph does not appear when you generate this report for a VMware ESX system.

    • Network Device Interfaces
      The Resource Usage statistics for all Network Device interfaces associated with the selected Elements. The following statistics are included:

      Port Namethe name of the port
      Typethe type of port
      Usagethe percentage of the port's maximum throughput that was used by inbound and outbound packets
      In Ratethe average throughput of inbound packets, in Mbps
      In Usagethe percentage of the port's maximum throughput that was used by inbound packets
      Out Ratethe average throughput of outbound packets, in Mbps
      Out Usage %the percentage of the port’s maximum throughput that was used by outbound packets
      Errors #/secthe average number of errors per second
      Discards #/secthe average number of packets discarded per second
      Statusthe port status
    Optionally, click Select All to generate a report on all of the options listed above.
  4. If you selected more than one report option and plan to report on more than one system, you can optionally click the Group report options by system checkbox.
    Selecting this option combines the metrics for each system for which you are generating the report.
  5. To generate reports for systems in specific groups, select the groups from the List of Groups area.
  6. To generate reports for one or more views, select the groups from the List of Views area.
    See Working with Views for more information about views.
  7. If you are generating reports for specific systems, select the systems from the List of Systems.
  8. Select a report generation option. See Report Generation Options for details.
  9. If you want to save the report or schedule it to run at a specific time or interval, complete the settings in the Save Reports section of the subpanel.
    See Saving Reports and Scheduling Reports for more information.

Resource Hot Spot Report

The Resource Hot Spot report is a key checkpoint report that allows you to quickly identify servers and network devices across your enterprise that may be having performance issues, so you can immediately start working to identify what may be causing them.

The Resource Hot Spot report helps you answer the following types of questions:

  • Which servers and network devices in my infrastructure were the top consumers in various resource usage categories?
  • Which servers are running short on memory, or are overworked?
  • Which VMs' processes need to be shared with another instance?
  • Are all network devices correctly configured?
  • For resource-strained Elements, is there a configuration issue or is it a resourcing issue?
The resource consumer summaries rank physical and virtual servers as well as network devices in various resource-related categories, allowing you to correlate top-ranking consumers across categories to identify specific problems. The summaries are populated irrespective of whether critical outages occurred, or the infrastructure experienced 100% uptime; this allows you to identify potentially strained resources before they enter warning-level states.

The report is also a valuable investigative tool that helps you quickly focus on the parts of your infrastructure that require troubleshooting. The report can be configured to include full listings of threshold-violating servers and network devices based on key resource-usage metrics such as memory and CPU usage, port throughput caps, or packet-issue counts. The high, low, and average for these metrics are presented, along with historical graphs for offending metrics; these details can help you confirm whether sustained resource strain, or wild swings are caused by resourcing deficits or configuration errors.

The Resource Hot Spot report is also a key starter report, as it is automatically created and saved for new up.time installations. This report provides a summary of top resource users for the week. By default, a PDF version of the report is emailed to the SysAdmin user group.

The following are portions of an example Resource Hot Spot report: 

 

 

Info

The Resource Hot Spot report is a default report that is automatically created and saved for weekly generation on new up.time installations, beginning the third day after up.time was first installed.

 

Resource Hot Spot Report Details

The following information comprises the Resource Hot Spot report:

Servers
Top ServersOf the servers included in the report, the top five resource consuming servers in terms of CPU, memory, swap usage, and disk usage. These servers are listed regardless of whether they violated resource usage thresholds set during report configuration; if your entire infrastructure is meeting your resource usage criteria for the report, the top-five servers are still included in the summary for each category.
CPUThe percentage of CPU capacity used during the defined time period. In the Top Servers summary, this is an average value for the time period.
MemThe percentage of memory used by processes for the defined time period. In the Top Servers summary, this is an average value for the time period. 
Swap UsageThe percentage of memory swap space used during the defined time period. In the Top Servers summary, this is an average value for the time period.
Disk BusyThe percentage of time the server disk is handling transactions in progress for the defined time period. In the Top Servers summary, this is an average value for the time period.
Servers with High CPU Usage

A listing of all servers included in the report whose average CPU usage for the time period exceeded the threshold defined during report configuration. Each server's entry includes the following information to help correlate the violating metric with other metrics or events:

  • the violating CPU usage percentage (highlighted)
  • historical values for this metric, graphed over the defined time period
  • the minimum and maximum values for the metric during the time period
  • minimum, maximum, and average values for other resource usage metrics
Servers with High Memory Usage

A listing of all servers included in the report whose average memory usage for the time period exceeded the threshold defined during report configuration. Each server's entry includes the following information to help correlate the violating metric with other metrics or events:

  • the violating memory usage percentage (highlighted)
  • historical values for this metric, graphed over the defined time period
  • the minimum and maximum values for the metric during the time period
  • minimum, maximum, and average values for other resource usage metrics
Servers with High Swap Usage

A listing of all servers included in the report whose average memory swap space usage for the time period exceeded the threshold defined during report configuration. Each server's entry includes the following information to help correlate the violating metric with other metrics or events:

  • the violating memory swap space usage percentage (highlighted)
  • historical values for this metric, graphed over the defined time period
  • the minimum and maximum values for the metric during the time period
  • minimum, maximum, and average values for other resource usage metrics
Servers with High Disk Busy

A listing of all servers included in the report whose average disk processing for the time period exceeded the threshold defined during report configuration. Each server's entry includes the following information to help correlate the violating metric with other metrics or events:

  • the violating disk activity percentage (highlighted)
  • historical values for this metric, graphed over the defined time period
  • the minimum and maximum values for the metric during the time period
  • minimum, maximum, and average values for other resource usage metrics
Network Devices
Top Network DevicesOf the network-device type Elements included in the report, the five most inefficient network devices in terms of in rate, out rate, error count, and discards. These network devices are listed regardless of whether they violated throughput or error thresholds set during report configuration; if all of your network devices are passing the criteria for the report, the top-five network devices are still included in the summary for each category.
In Rate %The percentage of the network device's maximum throughput, on a per port basis, that was used by inbound packets during the defined time period.
Out Rate %The percentage of the network device's maximum throughput, on a per port basis, that was used by outbound packets during the defined time period.
Errors per secThe average number of errors encountered per second, on a per port basis, during the defined time period.
Discards per secThe average number of packets discarded per second, on a per port basis, during the defined time period.
Network Devices with High In Rate

A listing of all network devices included in the report whose average in-rate percentage for the time period exceeded the threshold defined during report configuration. Each network device's entry includes the following information to help correlate the violating metric with other metrics or events:

  • the violating in-rate percentage (highlighted)
  • historical values for this metric, graphed over the defined time period
  • the minimum and maximum values for the metric during the time period
  • minimum, maximum, and average values for other resource usage metrics
Network Devices with High Out Rate

A listing of all network devices included in the report whose average out-rate percentage for the time period exceeded the threshold defined during report configuration. Each network device's entry includes the following information to help correlate the violating metric with other metrics or events:

  • the violating out-rate percentage (highlighted)
  • historical values for this metric, graphed over the defined time period
  • the minimum and maximum values for the metric during the time period
  • minimum, maximum, and average values for other resource usage metrics
Network Devices with High Errors

A listing of all network devices included in the report whose average error-per-second count for the time period exceeded the threshold defined during report configuration. Each network device's entry includes the following information to help correlate the violating metric with other metrics or events:

    • the violating error count (highlighted)
    • historical values for this metric, graphed over the defined time period
    • the minimum and maximum values for the metric during the time period
    • minimum, maximum, and average values for other resource usage metrics
Network Devices with High Discards

A listing of all network devices included in the report whose average discarded-packet count for the time period exceeded the threshold defined during report configuration. Each network device's entry includes the following information to help correlate the violating metric with other metrics or events:

  • the violating discarded packet count (highlighted)
  • historical values for this metric, graphed over the defined time period
  • the minimum and maximum values for the metric during the time period
  • minimum, maximum, and average values for other resource usage metrics
Creating a Resource Hot Spot Report
To create a Resource Hot Spot report, do the following:
  1. On the Reports tab, click Resource Hot Spot, which is found in the Performance and Analysis section of the reports tree panel.
  2. In the date and time range section, select a reporting window.
    For more information, see Understanding Dates and Times.
  3. In the Report Options section, configure which components comprise your report:
    • top-five lists for servers or network devices in various resource-usage categories
    • comprehensive lists of Elements that are experiencing performance issues in various resource-usage categories
    • for the Element list, the threshold used to determine which are experiencing performance issues
    By default, the Resource Hot Spot report is configured to display both servers and network devices in the Top Resource Consumers Summary, and list server-type Elements that violate various resource-usage thresholds. For information on these report components and thresholds, see Resource Hot Spot Report Details.
  4. Determine which Elements are included in the resource hot-spot assessment by selecting Infrastructure Groups, Element Views, or individual Elements from the following sections:
    • List of Groups
    • List of Views
    • List of Elements
  5. Continue with the desired report generation process:

Resource Cold Spot Report

The Resource Cold Spot report is a key checkpoint report that provides resource utilization less than the specified metrics, or rather the inverse of the Resource Hot Spot report.

The Resource Cold Spot report helps you answer the following types of questions:

  • Which servers and network devices in my infrastructure were the bottom consumers in various resource usage categories?
  • Which servers have unused memory, or are underworkedunder worked?
  • Are all network devices correctly configured?

The resource consumer summaries rank physical and virtual servers as well as network devices in various resource-related categories, allowing you to correlate bottom-ranking consumers across categories to identify availability.

The report is also a valuable investigative tool that helps you quickly focus on the parts of your infrastructure that require troubleshooting. The report can be configured to include full listings of servers and network devices based on key resource-usage metrics such as memory and CPU usage, port throughput caps, or packet-issue counts. The high, low, and average for these metrics are presented, along with historical graphs for offending metrics.

The Resource Cold Spot report is also a key starter report, as it is automatically created and saved for new up.time installations. This report provides a summary of bottom resource users for the week. By default, a PDF version of the report is emailed to the SysAdmin user group.

 

Info

The Resource Cold Spot report is a default report that is automatically created and saved for weekly generation on new up.time installations, beginning the third day after up.time was first installed.

 

Resource Cold Spot Report Details

The following information comprises the Resource Cold Spot report:

Servers
Bottom ServersOf the servers included in the report, the bottom five resource-consuming servers in terms of CPU and memory. These servers are listed regardless of whether they violated resource usage thresholds set during report configuration; if your entire infrastructure is meeting your resource usage criteria for the report, the bottom-five servers are still included in the summary for each category.
CPUThe percentage of CPU capacity used during the defined time period. In the Bottom Servers summary, this is an average value for the time period.
MemThe percentage of memory used by processes for the defined time period. In the Bottom Servers summary, this is an average value for the time period. 
Servers with Low CPU Usage

A listing of all servers included in the report whose average CPU usage for the time period was less than the threshold defined during report configuration. Each server's entry includes the following information to help correlate the metric with other metrics or events:

  • the violating CPU usage percentage (highlighted)
  • historical values for this metric, graphed over the defined time period
  • the minimum and maximum values for the metric during the time period
  • minimum, maximum, and average values for other resource usage metrics
Servers with Low Memory Usage

A listing of all servers included in the report whose average memory usage for the time period was less than the threshold defined during report configuration. Each server's entry includes the following information to help correlate the metric with other metrics or events:

  • the violating memory usage percentage (highlighted)
  • historical values for this metric, graphed over the defined time period
  • the minimum and maximum values for the metric during the time period
  • minimum, maximum, and average values for other resource usage metrics
Network Devices
Bottom Network DevicesOf the network-device type Elements included in the report, the five least inefficient network devices in terms of in rate, out rate, error count, and discards. These network devices are listed regardless of whether they violated throughput or error thresholds set during report configuration; if all of your network devices are passing the criteria for the report, the bottom-five network devices are still included in the summary for each category.
In Rate %The percentage of the network device's maximum throughput, on a per port basis, that was used by inbound packets during the defined time period.
Out Rate %The percentage of the network device's maximum throughput, on a per port basis, that was used by outbound packets during the defined time period.
Network Devices with Low In Rate

A listing of all network devices included in the report whose average in-rate percentage for the time period was less than the threshold defined during report configuration. Each network device's entry includes the following information to help correlate the metric with other metrics or events:

  • the violating in-rate percentage (highlighted)
  • historical values for this metric, graphed over the defined time period
  • the minimum and maximum values for the metric during the time period
  • minimum, maximum, and average values for other resource usage metrics
Network Devices with Low Out Rate

A listing of all network devices included in the report whose average out-rate percentage for the time period was less than the threshold defined during report configuration. Each network device's entry includes the following information to help correlate the metric with other metrics or events:

  • the violating out-rate percentage (highlighted)
  • historical values for this metric, graphed over the defined time period
  • the minimum and maximum values for the metric during the time period
  • minimum, maximum, and average values for other resource usage metrics
Creating a Resource Cold Spot Report
To create a Resource Cold Spot report, do the following:
  1. On the Reports tab, click Resource Cold Spot, which is found in the Performance and Analysis section of the reports tree panel.
  2. In the date and time range section, select a reporting window.
    For more information, see Understanding Dates and Times.
  3. In the Report Options section, configure which components comprise your report:
    • bottom-five lists for servers or network devices in various resource-usage categories
    • comprehensive lists of Elements that are experiencing performance issues in various resource-usage categories
    • for the Element list, the threshold used to determine which are experiencing performance issues
    By default, the Resource Cold Spot report is configured to display both servers and network devices in the Bottom Resource Consumers Summary, and list server-type Elements that violate various resource-usage thresholds. For information on these report components and thresholds, see Resource Cold Spot Report Details.
  4. Determine which Elements are included in the resource cold-spot assessment by selecting Infrastructure Groups, Element Views, or individual Elements from the following sections:
    • List of Groups
    • List of Views
    • List of Elements
  5. Continue with the desired report generation process:

Multi-System CPU Report

The Multi-System CPU report charts and compares the CPU performance statistics from multiple systems in your environment. These statistics indicate whether the systems are exhibiting balanced behavior, or if processes are forced off CPUs in certain circumstances.

Creating a Multi-System CPU Report

To create a Multi-System CPU report, do the following:

  1. In the Reports Tree panel, click Multi-System CPU.
  2. In the Date and Time Range area, select the dates and times on which to report.  For more information, see Understanding Dates and Times.
  3. If you want the report to only include data from certain hours during the day, select those hours from the dropdown lists in the Daily Hours section.
    For example, if you want to report to cover the hours from 1:00 a.m. to 1:00 p.m., select 1:00 from the Start dropdown list, and 13:00 from the End dropdown list.
  4. If you want to generate reports for systems in specific groups, select the groups from the List of Groups area.
  5. To generate reports for one or more views, selecft select the groups from the List of Views area.
    See Working with Views for more information about views.
  6. If you are generating reports for specific systems in your environment, select them from the List of Systems.
  7. Select a report generation option. See Report Generation Options for details.
  8. To save the report or schedule it to run at a specific time or interval, complete the settings in the Save Reports section of the subpanel.
    See Saving Reports and Scheduling Reports for more information.

CPU Utilization Summary Report

The CPU Utilization Summary report generates a tabular summary of the CPU and memory consumption over a specific time period. Specifically, this report returns the following information:

  • number of CPUs on the server.
  • the total processor speed of all the CPUs, in MHz
  • the maximum, minimum, and average CPU use, expressed as a percentage
  • the maximum, minimum, and average memory use, expressed as a percentage
  • the maximum, minimum, and average page scan per second, expressed as a percentage
Creating a CPU Utilization Summary Report

To create a CPU Utilization Summary report, do the following:

  1. In the Reports Tree panel, click CPU Utilization Summary.
  2. In the Date and Time Range area, select the dates and times on which to report. For more information, see Understanding Dates and Times.
  3. Select one of the following options from the Sort by dropdown list to sort the results that up.time returns:
    • Average CPU (the default)
    • Hostname
    • # of CPUs
    • CPU Speed
    • Maximum CPU
    • Minimum CPU
    • Average Memory
    • Maximum Memory
    • Minimum Memory
    • Average Page Scan
    • Maximum Page Scan
    • Minimum Page Scan
  4. Select Ascending or Descending from the Sort Direction dropdown list.
  5. Optionally, in the Minimum sort value for inclusion field enter a value for the sort threshold.
    The report displays items from the Sort By list, whose value is equal to or greater than the value in this field. For example, if you chose # of CPUs from the Sort by list and set this field to 2, the report only displays systems with two or more CPUs.
  6. Select one or more of the following CPU statistics at which the report looks:
    • sys
      The percentage of CPU time that is used to carry out system processes.
    • usr
      The percentage of CPU time that is used to carry out user processes.
    • wio
      The percentage of CPU time that could be handling processes, but which is waiting for I/O operations to complete.
  7. Select one or more of the following statistics on which to report:
    • CPU
      The percentage of CPU resources that are used.
    • Memory
      The percentage of system memory that is used.
    • Page Scans
      The number of page scans per second.

      Info
      The statistic you select must match the sort criteria that you selected in step 4. For example, if your sort criteria is Average CPU you must also select the CPU statistic. Otherwise, an error message appears when you try to generate the report.
  8. Optionally, in the Architectures to exclude field enter either the name of a system architecture or a regular expression that up.time uses to ignore certain system architectures when generating the report.
    For example, if you want to exclude all Solaris systems from the report, enter SunOS in the field.

    Info

    up.time determines the architecture of a system by checking the output of the uname -a command on UNIX or Linux, or by analyzing one or both of the following Windows registry keys:

    HKEY_LOCAL_MACHINE\\Software\\Microsoft\\
    WindowsNT\\CurrentVersion
    HKEY_LOCAL_MACHINE\\Software\\Microsoft\\
    Windows\\CurrentVersion
  9. If you want to generate reports for systems in specific groups, select the groups from the List of Groups area.
  10. To generate reports for one or more views, select the groups from the List of Views area.
    See Working with Views for more information about views.
  11. If you are generating reports for specific systems in your environment, select them from the List of Systems.
  12. Select a report generation option. See Report Generation Options for details.
  13. To save the report or schedule it to run at a specific time or interval, complete the settings in the Save Reports section of the subpanel.
    See Saving Reports and Scheduling Reports for more information.

CPU Utilization Ratio Report

The CPU Utilization Ratio report charts, in a table, the ratio of the percentage of CPU usage over a specified period of time. The ratio is derived by dividing the percentage of system time that is used by the percentage of user time. For example, if the amount of system time that is used is 22.12% and the amount of user time is 5.2%, then the CPU utilization ratio is 4.25.

This report contains the following information:

  • the names of the hosts for which the report is generated
  • the percentage of CPU time that is used to carry out user processes ( USR % )
  • the percentage of CPU time that is use to carry out system processes ( SYS % )
  • the CPU utilization ratio for each host, which is derived by dividing SYS % by USR %=
Creating a CPU Utilization Ratio Report
To generate a CPU Utilization Ratio report, do the following:
  1. In the Reports Tree panel, click CPU Utilization Ratio.
  2. In the Date and Time Range area, select the dates and times on which to report. For more information, see Understanding Dates and Times.
  3. If you want the report to only include data from certain hours during the day, select those hours from the dropdown lists in the Daily Hours section.
    For example, if you want to report to cover the hours from 1:00 a.m. to 1:00 p.m., select 1:00 from the Start dropdown list, and 13:00 from the End dropdown list.
  4. Optionally, enter a value in the Highlight ratios over threshold field.
    Any ratios that exceed the value in this field are highlighted in the report. For example, if you enter 2 and a server returns a ratio of 3.5%, that ratio is highlighted.
  5. If you want to generate reports for groups of systems, select the groups from the List of Groups area.
  6. To generate reports for one or more views, select the groups from the List of Views area.
    See Working with Views for more information about views.
  7. If you are generating reports for specific systems in your environment, select them from the List of Systems.
  8. Select a report generation option. See Report Generation Options for details.
  9. To save the report or schedule it to run at a specific time or interval, complete the settings in the Save Reports section of the subpanel.
    See Saving Reports and Scheduling Reports for more information.

Wait I/O Report

The Wait I/O report enables you to determine the amount of time that processes spend waiting on I/O from a system device.

The Wait I/O report contains the following information:

  • the names of the hosts for which the report is generated
  • the average, maximum, and minimum wait I/O times expressed as percentages
Creating a Wait I/O Report
To create a Wait I/O report, do the following:
  1. In the Reports Tree panel, click Wait I/O .
  2. In the Date and Time Range area, select the dates and times on which to report. For more information, see Understanding Dates and Times.
  3. If you want the report to only include data from certain hours during the day, select those hours from the dropdown lists in the Daily Hours section.
    For example, if you want to report to cover the hours from 1:00 a.m. to 1:00 p.m., select 1:00 from the Start dropdown list, and 13:00 from the End dropdown list.
  4. Optionally, enter a value in the Highlight average WIO over threshold field.
    Any system with an average Wait I/O percentage that exceeds the value that you enter in this field is highlighted in red in the report. As well, the following text appears in the header of the report:
    Systems with an Average Wait I/O over x.x% are highlighted
    Where x.x is the percentage that you entered in this field.
  5. If you want to generate reports for systems in specific groups, select the groups from the List of Groups area.
  6. To generate reports for one or more views, select the groups from the List of Views area.
    See Working with Views for more information about views.
  7. If you are generating reports for specific systems in your environment, select them from the List of Systems.
  8. Select a report generation option.See Report Generation Options for details.
  9. Do one of the following:
    • Click the Generate Report button.
    • Enter a name for the report in the Save to My Portal As field, and optionally enter text in the Report Description field. Then, click Save Report.
      The report parameters are saved to the My Portal panel. Doing this does not generate the report.
  10. To schedule the saved report to run at a specific time or interval, click the Scheduled checkbox.
    See Scheduling Reports for more information on configuring a scheduled report.

Inventory Report

The Inventory report provides details about the composition of your monitored infrastructure by operating system, across physical and virtual Elements. The report contents can optionally be organized by group, and can include individual Element entries.

These different reporting options allow you to confidently assess your inventory from a variety of perspectives, and help you answer the following types of questions:

  • How many older versions of the up.time Agent are deployed on my systems?
  • What is the operating system breakdown across my infrastructure, both virtualized, and on physical systems?
  • I need to upgrade a particular OS version; which systems are candidates for this deployment?
Inventory Report Information
Info

Because the Inventory report displays all monitored Elements, the report is intended for system administrators. Non-administrative up.time users who do not have permission to view all Elements cannot view complete inventory listings.

The following information can be displayed in the Inventory Report when you select Show Operating System Summary:

Operating System Summary

unique breakdown of physical and virtual Elements, with totals by OS, and component totals for OS versions

Physical Elements

the total number of systems-type Elements (i.e., not network devices, Applications, and SLAs)

this total includes virtual machines that are not managed by a VMware vCenter server Element (e.g., LPARs or VMware VMs manually added to up.time, and not through vSync)

Virtual Elements

the total number of Elements running on VM instances (i.e., VM instances with their own UUID)

Operating System

the detected operating system, including VMware environments

Version

the detected operating system version; build version details are listed if available

Element Name

the Element’s host name

Architecture

the detected hardware platform type on which the Element’s CPUs are running

Agent Version

if applicable, the version of the up.time Agent that is running on the Element

Added Date

the date the Element was added to up.time monitored inventory

Group

the Element’s My Infrastructure group name

The following information can be displayed in the Inventory Report when you select Show Element Type Summary:

Element Type Summary

unique breakdown of physical and virtual Elements by type, with when the element was added, monitoring status, which group contains each element, and component totals for each Element type

Agent Elements

contains Elements identified by up.time as Agents

vSphere Elements

contains Elements identified by up.time as vSpheres

Virtual Machine Agentless Elementscontains Elements identified by up.time as Agentless Virtual Machines
VMware vCenter Server Elementscontains Elements identified by up.time as VMware vCenter Servers
Network Device Elementscontains Elements identified by up.time as Network Devices

Element Name

the Element’s host name

OS Type

the detected operating system, including VMware environments

Added Date

the date the Element was added to up.time monitored inventory

Monitored

whether the Element is monitored (True) or not monitored (False)
Group

the Element’s My Infrastructure group name

The following information can be displayed in the Inventory Report when you select Show Monitor Summary:

Monitor Summary

unique breakdown of physical and virtual Elements by type, with element name, assigned Service Monitor, whether the Element is monitored and for what period of time, whether there are associated Alert and Action Profiles, and component totals for each Element Service Monitor

Agent Elements

contains Elements identified by up.timeas time as Agents

vSphere Elements

contains Elements identified by up.timeas time as vSpheres

Virtual Machine Agentless Elementscontains Elements identified by up.timeas time as Agentless Virtual Machines
VMware vCenter Server Elementscontains Elements identified by up.timeas time as VMware vCenter Servers
Network Device Elementscontains Elements identified by up.timeas time as Network Devices

Element Name

the Element’s host name

Service Monitor

the name of the service monitor assigned to this Element

Monitored

whether the Element is monitored (True) or not monitored (False)

Notification

whether notifications are issued for this Element's service monitor (Yes) or notifications are not issued (No) regardless of status or interval

Monitoring Period

the Element's service monitor time period at which up.time sends alerts

Alert Profile

whether the Element has an associated alert profile (Yes) or not (No)

Alert Profiles are templates that tell up.time how to react to various alerts that are generated by service checks.

Action Profile

whether the Element has an associated action profile (Yes) or not (No)

Action Profiles are templates that direct up.time when it encounters a problem on a monitored system.

 

Creating an Inventory Report
To create an Inventory report, do the following:
  1. In the Reports Tree panel, click Inventory Report.
  2. In the Date and Time Range area, select the dates and times on which to report. For more information, see Understanding Dates and Times.
  3. Optionally select the Don’t List Individual Elements check box to restrict the report to inventory summaries.
  4. Optionally select the Group by Selected System Groups check box to organize the report by group.
  5. If you want to generate reports for systems in specific groups, select the groups from the List of Groups area.
  6. To generate reports for one or more views, select the groups from the List of Views area.
    See Working with Views for more information about views.
  7. If you are generating reports for specific Elements in your environment, select them from the List of Elements.
  8. Select a report generation option.See Report Generation Options for details.
  9. Do one of the following:
    • Click the Generate Report button.
    • Enter a name for the report in the Save to My Portal As field, and optionally enter text in the Report Description field. Then, click Save Report.
      The report parameters are saved to the My Portal panel. Doing this does not generate the report.
  10. To schedule the saved report to run at a specific time or interval, click the Scheduled checkbox.
    See Scheduling Reports for more information on configuring a scheduled report.

Service Monitor Metrics Report

You can configure the up.time service monitors to retain data, which is saved to the up.time DataStore for later use. The Service Monitor Metrics report visualizes the retained data in a line chart.

For example, if you have configured a service monitor to retain response time data then this report charts any changes in the response time (in milliseconds) that have occurred over the time period that you specified for the report.

Creating a Service Monitor Metrics report is a two-step process:

  • enter the basic parameters for the report
  • select the values for the retained on which you want to report
Creating Service Monitor Metrics Reports
To create a Service Monitor Metrics report, do the following:
  1. In the Reports Tree panel, click Service Monitor Metrics.
  2. In the Date and Time Range area, select the dates and times on which to report. For more information, see Understanding Dates and Times.
  3. If you want to generate reports for systems in specific groups, select the groups from the List of Groups area.
  4. To generate reports for one or more views, select the groups from the List of Views area.
    See Working with Views for more information about views.
  5. If you are generating reports for specific systems in your environment, select them from the List of Elements.
  6. Click Go to page 2.
    A table containing the current retained service metrics appears in the Service Metrics subpanel.
  7. Click the checkboxes in the Select column to select the variables on which you want to report.
  8. Optionally, select one of the following:
    • Show all non-ranged metrics on one chart
      This option combines all of the variables you selected in one chart. Any ranged metrics appear in their own charts.
    • Display charts as stacked area
      Each chart in the report has two or more data series stacked on top of each other, rather than the line graph that usually appears in the report.
  9. To save the report, do the following:
    • Enter a name for the report in the Save to My Portal As field.
    • Optionally, enter text in the Description field.
    • Click Save Report.
      The report parameters are saved to the My Portal panel. Doing this does not generate the report.
  10. To schedule the saved report to run at a specific time or interval, click the Scheduled checkbox.
    See Saving Reports and Scheduling Reports for more information.

...

Reports for J2EE Applications

The following reports enable you to visualize any performance problems with applications that are running a J2EE environments:

WebSphere Report

The WebSphere report charts a set of counters that provide insight into the health and performance of a WebSphere Application Server. Depending on the number of options that you select, the report can become quite long and can take considerable time to generate. For most options, the report contains charts for two or more metrics.

Creating a WebSphere Report
To create a WebSphere report, do the following:
  1. In the Reports Tree panel, click WebSphere.
  2. In the Date and Time Range area, select the dates and times on which to report. For more information, see Understanding Dates and Times.
  3. Select one or more of the following report options:
    • Thread pool
      A set of counters that report on the number of connection threads that were created or destroyed, that are concurrently active or are hung, that are in the thread pool, or time that are in use.
    • JDBC Connection Pool
      A set of counters that monitor the performance of JDBC data sources.
    • Enterprise Beans
      A set of counters that report the following: load values, response times, and life cycle activities for enterprise Java beans.
    • JVM Runtime
      A set of counters that monitor the performance of the Java Virtual Machine (JVM) that is running on the WebSphere server.
    • Transaction Manager
      A set of counters that report on the status of global, local, and concurrent transactions.
    • Servlet Session Manager
      A set of counters that report on usage information from the HTTP servlets that are running on the server.
    Optionally, click Select All to generate a report on all of the options listed above.
  4. If you selected more than one report option and plan to report on more than one system, you can optionally click the Group report options by system checkbox.
    Selecting this option combines the metrics for each system for which you are generating the report.
  5. To generate reports for systems in specific groups, select the groups from the List of Groups area.
  6. To generate reports for one or more views, select the groups from the List of Views area.
    See Working with Views for more information about views.
  7. If you are generating reports for specific systems, select the systems from the List of Systems.
  8. Select a report generation option. See Report Generation Options for details.
  9. If you want to save the report or schedule it to run at a specific time or interval, complete the settings in the Save Reports section of the subpanel.
    See Saving Reports and Scheduling Reports for more information.
Using the WebSphere Report

Because WebSphere is large and complex, it can be difficult to pinpoint the source of a problem with the server or an application running on the server. This is especially true when that problem is intermittent. Watching for problems in real time only gives you a snapshot of the problem. The up.timeWebSphere time WebSphere report, on the other hand, gives you a detailed historical perspective of the problem. Using the information in the report, you can find the source of the problem.

For example, users have trouble working with an application that intensively uses a database. Checking the Connection Pool charts section of a WebSphere report could indicate the source of the problem - the database has reached its maximum number of connections.

You can then adjust the size of the database connection pool to allow more connections.

Or, if a WebSphere application is using a large amount of memory you could check the JVM charts section of the report. If there are spikes in the heap size or memory usage of the JVM, you can tune the JVM to ensure that it is working at optimal levels.

WebLogic Report

The WebLogic report charts a set of metrics (see WebLogic for details) that provide insight into the health and performance of a WebLogic server. Using the WebLogic report, you can pinpoint problem areas on your WebLogic server and quickly determine how to fix those problems.

Depending on the number of options that you select, the report can become quite long and can take considerable time to generate. For most options, the report contains charts for two or more metrics.

Creating a WebLogic Report
To create a WebLogic report, do the following:
  1. In the Reports Tree panel, click WebLogic.
  2. In the Date and Time Range area, select the dates and times on which to report. For more information, see Understanding Dates and Times.
  3. In the Report Options area, select one or more of the following options:
    • Thread pool
      The report charts the number of pending request in the thread pool, as well as the free size of the pool.
    • Server Stats
      The report charts the number of connection requests that WebLogic accepts before refusing additional requests, as well as the number of open sockets to the server.
    • JDBC Connection Pool
      The report charts the number of active and leaked connections to the server, as well as the size of the connection pool, the number of connections that are waiting or delayed, and the number of 
      failures to reconnect to the server.
    • Enterprise Beans
      The report charts the number of Enterprise Java Beans (EJB) that are active or were moved to secondary storage, the number of time that a container can and cannot find an EJB in the cache, as well as the total number of EJBs in the cache.

      This report returns information for:
      •  Stateful EJBs, which hold data for a client between calls to the EJB. Stateful EJBs can use considerable amount of server resources.
      • Stateless EJBs, which hold data for only one call to the EJB, and then deletes that data. Stateless EJBs use fewer system resources than stateful EJBs
    • JVM Runtime
      The report charts the heap size (in kilobytes) of the Java Virtual Machine (JVM) on the WebLogic server, as well as amount memory (in kilobytes) available to the JVM.
    • Transaction Manager
      The report charts the number of transactions that were committed or completed successfully, as well as total number of transactions that are rolled back.
    • Servlets
      The report charts the number of requests that were made to the HTTP servlets that are running on the WebLogic server.

      Optionally, click Select All Options to use all of the options that are listed above.
  4. If you want to generate reports for groups of systems, select the groups from the List of Groups area.
  5. To generate reports for one or more views, select the groups from the List of Views area.
    See Working with Views for more information about views.
  6. If you are generating reports for specific systems in your environment, select them from the List of Systems and Nodes.
  7. Select a report generation option. See Report Generation Options for details.
  8. To save the report or schedule it to run at a specific time or interval, complete the settings in the Save Reports section of the subpanel.
    See Saving Reports and Scheduling Reports for more information.
Using the WebLogic Report

Because WebLogic is large and complex, it can be difficult to pinpoint the source of a problem with the server or an application running on the server. This is especially true when that problem is intermittent. Watching for problems in real time only gives you a snapshot of the problem. The up.timeWebLogic time WebLogic report, on the other hand, gives you a detailed historical perspective of the problem. Using the information report, you can find the source of the problem.

For example, users have trouble logging into an application that is running on the WebLogic server. Checking the Connection Pool charts section of a WebLogic report, you might see that the size of the connection pool has reached its maximum, and that there are a large number of connections that are waiting in the pool. From there, you can then adjust the size of the connection pool to allow more connections.

Or, if a WebLogic application is using a large amount of memory you could check the JVM charts section of the report.

If there are increases or sudden spikes in the heap size or memory usage of the JVM, then you can tune the JVM to ensure that it is working at optimal levels.

Reports for Virtual Environments

Virtualization platforms such as VMware vSphere enable you to consolidate servers and applications in a virtual environment. Using virtual machine managers such as VMware ESX, you can run multiple servers or applications on a single system, but without using as much hardware. Each server or application runs in its own VMware instance. You can use VMware vSphere to manage and monitor ESX servers, as well as allocate resources among virtual machines.

up.time ’s VMware and pSeries reports enable you to visualize the performance of systems that are consolidated on virtual machines, whether using VMware or IBM pSeries Logical Partitions (LPARs):

VM Sprawl Report

The VM Sprawl report helps you assess the extent of sprawl across your virtual infrastructure, and provides you with the information needed to reduce it. Using the report, you can perform the following types of tasks:

  • see which VMs are underused, and which VMs’ tasks should be consolidated elsewhere
  • create an inventory of VMs that are always off or suspended, thus were unnecessarily created
  • see which VMs were not powered on recently
  • audit or verify VM creation and destruction balance
  • plot VM population trends to see if sprawl is growing or reduced

Depending on how it is configured the VM Sprawl report consists of at least one of the following components:

  1. monthly VM population trends for up to the last year
    For each month, stacked bars show the following VM totals:
    • created during that month and are currently running
    • created during that month and are currently suspended or powered off
    • destroyed during that month
    • created and destroyed during that same month
  2. a list of VMs created during the time period
  3. a list of VMs destroyed during the time period
  4. lists summarizing various VM power state scenarios:
    • existing VMs created that were powered off or suspended for 20% or more of the time, during the time period
    • existing VMs that were not powered on during the time period
    • existing VMs that were in a suspended state for the time period
Creating a VM Sprawl Report
To create a VM Sprawl report, do the following:
  1. In the Reports Tree panel, click VM Sprawl.

  2. In the Date and Time Range area, select the dates and times on which to report. For more information, see Understanding Dates and Times.
  3. In the Report Options section, select which types of VM population totals you would like to include in the report.
  4. Select the Elements whose child-object VMs you would like to include in the report totals.
    In most cases, for the greatest visibility with a high-level view, the selected Element is most likely be a VMware vCenter server or datacenter Element.
  5. Select a report generation option. See Report Generation Options for details.
  6. Do one of the following:
    • Click the Generate Report button.
    • Enter a name for the report in the Save to My Portal As field, and optionally enter text in the Report Description field. Then, click Save Report.
      The report parameters are saved to the My Portal panel. Doing this does not generate the report.
  7. To schedule the saved report to run at a specific time or interval, click the Scheduled checkbox.
    See Scheduling Reports for more information on configuring a scheduled report.

VM Workload Report

The VMware vSphere workload report provides a broad view of workloads across your entire virtual infrastructure. For selected Elements, it includes a resource usage overview (CPU, memory, disk, and network). It also includes detailed resource usage charts for selected Elements' child objects in the vSphere hierarchy.

Info

For reporting periods, total resource usage is reported regardless of how the VMware vSphere object child objects change during that time period. For example, a four-week overview chart for an ESX server includes performance of VMs that have since migrated.

Using this report, you can visualize resource usage at the datacenter, cluster or ESX server level, as well as with resource pools, vApps, and virtual machines. You can also understand how these Elements' respective child objects contribute to their usage levels.

vSphere Workload Report Metrics

The following metrics can be displayed in a VM Workload report:

 

CPU Usage

the following is shown for the interval:

  1. for ESX servers, the total CPU capacity, in GHz
  2. the current amount of CPU resources, in GHz, used by ESX hosts or VMs
  3. the total CPU capacity of the Element

Memory
Usage

the following is shown for the interval:

  1. for ESX servers, total memory capacity, in GB
  2. the amount of memory, in GB, used by ESX hosts or VMs
  3. the total memory capacity of the Element

Disk I/O

the rate, in MBps, at which ESX hosts or VMs are reading and writing data to and from disk

Network I/O

the rate, in Mbps, at which ESX hosts or VMs are receiving or transmitting data over the network

% Wait

the amount of time during the interval, as a percentage, that the VM or all VMs on an ESX host, resource pool or vApp had scheduled CPU time, but gave nothing to process

% Ready

the amount of time during the interval, as a percentage, that the VM or all VMs on an ESX host, resource pool or vApp were ready to process, but were not scheduled CPU time by the host

Info

For the % Wait and % Ready metrics, it is possible to be presented with values that exceed 100%. The underlying data used in the workload report's graphs are migrated from VMware vSphere via vSync; VMware conventions include percent-based metrics that can be greater than 100%. For example, refer to the VMware Technical Note, Performance Counters, at http://www.vmware.com/files/pdf/technote_PerformanceCounters.pdf.

 

Creating a VM Workload Report
To create a VM Workload report, do the following:
  1. In the Reports Tree panel, click VM Workload.
  2. In the Date and Time Range area, select the dates and times on which to report. For more information, see Understanding Dates and Times.
  3. Select the Elements you would like to include in the vSphere Workload report from the following sections where applicable:
    • List of vCenter Servers
    • List of ESX Servers
    • List of Datacenters
    • List of Clusters
    • List of Resource Pools
    • List of vApps
    • List of Virtual Machines
  4. Select which vSphere Element Summaries to Display.
    For each of the Elements you selected in the previous step, you can display resource usage summaries of their VMware vSphere child objects in the detailed sections of the report.
    For example, if you select a VMware vCenter server Element to be in the report, selecting the Datacenter and Cluster summary options includes summaries for datacenters and clusters that are child objects of the vCenter server. Note that selecting a VMware vSphere child object does not automatically include its own child objects (e.g., ESX servers that are part of a cluster); a selection exclusively includes that specific object.
    Only VMware vSphere child objects that are relevant to the parent are shown:
    • if you select the Datacenter summary option, VMware vCenter server Elements included in the report include resource usage summaries for its child datacenter objects
    • if you select the Cluster summary option, VMware vCenter server and datacenter Elements in the report include resource usage summaries for their child cluster objects
    • if you select the ESX Server summary option, datacenter and cluster Elements in the report include resource usage summaries for their child ESX server objects
    • if you select the Resource Pool or vApp summary options, any datacenter, cluster, or ESX server Elements included in this report include resource usage summaries of its top-level resource pools and vApps
    • if you select the Resource Pool or vApp summary options, any parent resource pool or vApp Elements included in this report include resource usage summaries for their child resource pools and vApps
    • if you select the Virtual Machine summary option, ESX servers, resource pools, and vApps included in this report include resource usage summaries for their child VMs
    • if you select the Virtual Machine summary option, datacenters and clusters included in this report include percent-ready and percent-wait summaries for its child VMs
  5. In the Report Options section, select whether to Show Overview Charts in the report.
    The overview charts consist of CPU, memory, disk, and network usage overviews for the defined time range.
  6. Select whether to Show Resource Utilization in the report.
    The resource utilization shows numeric summary information on CPU Utilization, Memory Utilization, and File System Utilization for the defined time range.
  7. Select a report generation option. See Report Generation Options for details.
  8. Do one of the following:
    • Click the Generate Report button.
    • Enter a name for the report in the Save to My Portal As field, and optionally enter text in the Report Description field. Then, click Save Report.
      The report parameters are saved to the My Portal panel. Doing this does not generate the report.
  9. To schedule the saved report to run at a specific time or interval, click the Scheduled checkbox.
    See Scheduling Reports for more information on configuring a scheduled report.

VM Workload (legacy) Report

A VMware server often slows down because an instance on the server is consuming large amounts of such system resources as CPU, disk I/O, and memory. The problem could lie with an instance that is currently slow or another instance on the same server. The VMware Workload report charts the workload of the server. You can also use the report to determine whether you are using a particular VMware server to its optimal capacity.

Info

This report provides information only about older, legacy VMware ESX type Elements that are part of your monitored infrastructure.

The VMware Workload report can be a useful tool for determining whether a VMware server is used to its optimal capacity. Consider the following example, in which the VMware Workload report returns the following information about the top ten CPU loads on the VMware server:

This graph indicates that, on average, the ten 10 most CPU-intensive instances use only 20% of the server’s CPU capacity. The CPU on the server can handle up to three to four times its current load.

The memory usage section of the report indicates that the instances are using roughly the same amount of memory:

The server appears to have an ample amount of memory available.

The report indicates that you can add more instances to the VMware server.

Creating a VM Workload (legacy) Report
To create a VM Workload (legacy) report, do the following:
  1. In the Reports Tree panel, click VM Workload (legacy).
  2. In the Date and Time Range area, select the dates and times on which to report. For more information, see Understanding Dates and Times.
  3. In the Report Options section, select one of the following:
    • Workload Profile - CPU
      The percentage of CPU time that is used by a VMware instance. This is a percentage of the available maximum amount of CPU time. This ensures that all of the CPU usage figures add up to the overall CPU usage of the server.
    • Workload Profile - Memory
      The amount of physical memory, in kilobytes, that is used by a VMware instance.
    • Workload Profile - Disk IO
      The amount of the disk I/O capacity, in kilobytes per second, that is used by a VMware instance.
    • Workload Profile - Network IO
      The amount of the network I/O capacity, in kilobits per second, that is used by a VMware instance.
    • Workload Profile - % Ready
      The amount of time that one or more instances running on an ESX server is ready to run, but cannot run because it cannot access the processor on the ESX server.
    • Workload Profile - % Used
      The percentage of CPU time that an instance running on an ESX server is using.
  4. If you want to generate reports for systems in specific groups, select the groups from the List of Groups area.
  5. To generate reports for one or more views, select the groups from the List of Views area.
    See Working with Views for more information about views.
  6. If you are generating reports for specific systems in your environment, select them from the List of Elements.
  7. Select a report generation option. See Report Generation Options for details.
  8. Do one of the following:
    • Click the Generate Report button.
    • Enter a name for the report in the Save to My Portal As field, and optionally enter text in the Report Description field. Then, click Save Report.
      The report parameters are saved to the My Portal panel. Doing this does not generate the report.
  9. To schedule the saved report to run at a specific time or interval, click the Scheduled checkbox.
    See Scheduling Reports for more information on configuring a scheduled report.

VM Density (legacy) Report

The VM Density report enables you to assess the carrying capacity and workload distribution of your ESX infrastructure. To accomplish this, virtual machine counts are tracked and reported on a daily basis, where the peak VM count for a given day is used as that day’s tally. The information available in the report includes the following:

  1. Virtual Infrastructure Density: The total number of virtual machines in relation to the total number of ESX servers over a given time period. A trend line is mapped onto the totals, indicating whether VM counts, and corresponding workloads, are increasing or decreasing in relation to available ESX server capacity.
  2. Total Virtual Machine Count: The total number of virtual machines running on all, or a group of, ESX servers. The VM totals are separated into individual ESX server totals.
  3. ESX Server Virtual Machine Count: The total number of virtual machines running on a specific ESX server.

Using this report, you can have a better understanding of virtualized workloads by seeing ESX server use and trends, and quantifying VM creation overall, and on a server-by-server basis.

Info

This report provides information only about older, legacy VMware ESX type Elements that are part of your monitored infrastructure.

Creating a VM Density Report
To create a VM Density report, do the following:
  1. In the Reports Tree panel, click VMware Infrastructure Density.
  2. In the Date and Time Range area, select the dates and times on which to report. For more information, see Understanding Dates and Times.
  3. In the Report Options section, indicate whether you want to Include Charts for Individual ESX Servers by selecting or clearing the check box.
    When this option is enabled, a separate chart with VM counts is created for each ESX server that is included in the report.
  4. In the Report Options section, select the level of granularity at which the virtual infrastructure density information is presented (i.e., daily, weekly, or monthly).
  5. If you want to generate reports for groups of systems, select the groups from the List of Groups area.
  6. To generate reports for one or more views, select the groups from the List of Views area.
    See Working with Views for more information about views.
  7. If you are generating reports for specific systems in your environment, select them from the List of Systems and Nodes.
  8. Select a report generation option. See Report Generation Options for details.
  9. To save the report or schedule it to run at a specific time or interval, complete the settings in the Save Reports section of the subpanel.
    See Saving Reports and Scheduling Reports for more information.

LPAR Workload Report

The LPAR Workload report charts the workload of the individual logical partitions (LPARs) on an IBM pSeries server. It does this by graphing the following workload data:

  • CPU
  • Memory
  • Network I/O
  • Disk I/O

Using the information in the report, you can ... This enables you to ...

Creating a Datastore Capacity Growth Report
To create a Datastore Capacity Growth report, do the following:
  1. In the Reports Tree panel, click LPAR Workload.
  2. In the Date and Time Range area, select the dates and times on which to report. For more information, see Understanding Dates and Times.
  3. Select one or more of the following report options:
    • CPU Workload
      The CPU entitlements of the LPARs, and their use of the entitlements.
    • Memory Workload
      The amount of memory, in kilobytes, that is used by the LPARs on the system.
    • Disk IO Workload
      The amount of data, measured in kilobytes per second, that is read from and written to the disk by the LPARs on the system.
    • Network IO Workload
      The amount of data, measured in kilobytes per second, that is sent and received over the network interface by the LPARs on the system.
      Optionally, click Select All to generate a report on all of the options that are listed above.
  4. If you selected more than one report option and plan to report on more than one system, you can optionally click the Group report options by system checkbox.
    Selecting this option combines the metrics for each system for which you are generating the report.
  5. To generate reports for systems in specific groups, select the groups from the List of Groups area.
  6. To generate reports for one or more views, select the groups from the List of Views area.
    See Working with Views for more information about views.
  7. If you are generating reports for specific systems, select the systems from the List of Systems.
  8. Select a report generation option. See Report Generation Options for details.
  9. If you want to save the report or schedule it to run at a specific time or interval, complete the settings in the Save Reports section of the subpanel.
    See Saving Reports and Scheduling Reports for more information.
Using the LPAR Workload Report

The LPAR Workload report takes the guesswork out of determining CPU entitlements for the LPARs on a pSeries server. The entitlements indicate the amount of CPU power that is assigned to an LPAR.

For example, you have an LPAR with hard entitlement (one that cannot use spare processing power from another CPU on the server) and its CPU usage is constantly at or near the maximum. In this case, you can either increase the CPU entitlement of the LPAR, or change it to a soft entitlement.

If, on the other hand, the LPAR has a soft entitlement (one which can use spare processing power from another CPU on the server) and its CPU usage is consistently at or greater than the entitlement, you can increase it.

...

Creating a Datastore Capacity Growth Report
To create a Datastore Capacity Growth report, do the following:
  1. In the Reports Tree panel, click Datastore Capacity Growth.
  2. In the Date and Time Range area, select the dates and times on which to report. For more information, see Understanding Dates and Times.
    If no data is available for the date range, the report displays a message indicating that there is no data for the time period.
  3. Optionally, in the Exclude datastores names like field, enter either the name of a datastore or a regular expression that up.time uses to ignore certain datastores when generating the report.
  4. Optionally, enter a value in the Exclude datastores over % full field.
    This value is expressed as a percentage. The report displays the information for datastores whose used disk space is less than the amount you enter in this field. For example, if you set this field to 45, the report only displays datastores whose percentage used values are less than or equal to 45%.
  5. If you are generating reports for specific datastores in your environment, select them from the List of Elements.
  6. Select a report generation option. See Report Generation Options for details.
  7. To save the report or schedule it to run at a specific time or interval, complete the settings in the Save Reports section of the subpanel.
    See Saving Reports and Scheduling Reports for more information.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

...