System Statistics(4.0)
- Jenni Wallin
constantly collects information from the different sub-systems and hosts within the installation system. Using System Statistics, you can view, export and import statistical information used for load balancing and performance tweaking.
There are three different types of statistics: host, pico instance, and workflow.
Toolbar
| Option | Description |
|---|---|
| Search | Allows users to search and return statistical results based on their search criteria. Refer to Searching the System Statistics for more information. |
| Refresh | Performs an update of all the statistical results being displayed. |
| Import | Allows users to import statistics that they had exported from System Statistics of the same |
| Export | Allows users to export the statistics on the selected time period. Refer to Exporting Statistics for more information. |
| Users can print the displayed statistics graphs and charts. |
Host Statistics
collects statistics from the different machines hosting a Platform or Execution Context. The statistics extracted from the machines can be the load of the CPU or the number of context switches.
uses the
vmstat UNIX command to collect the information. Ensure that this command is available in your servers to have statistics collected and to perform load-balancing work for workflows. Note that vmstat may not behave the same on different operating systems.
| Statistics | Description |
|---|---|
| CPU User Time | This value shows how much time was spent in non-kernel specific code. This value is displayed in percentage. 100% means that all processing power is spent. See CPU System Time as well. |
| CPU System Time | This value shows how much time was spent in kernel specific code, such as scheduling of different processes or network transfer. This value is displayed in percentage. 100% means that all processing power is spent. |
| Context Switches | The number of context switches per second. A context switch occurs when one process hands over information to another process. The more context switches, the less effective and scalable the system will be. |
| Swapped To Disk | The amount of data that was swapped out. A large value indicates that the system does not have enough RAM to manage the memory requirements of the different processes. |
| Swapped In From Disk | The amount of data that was read from swap. |
| Processes Waiting For Run | Shows how many processes that are waiting to run. A high number indicates that the machine is not fast enough to manage the load. |
| Processes In Sleep | The number of processes that are presently not doing anything. |
Pico Instance
Every minute, collects memory information from the different Java processes defining the Platform and the Execution Context. This information shows how much memory is used and how much memory that is available for the running process.
| Statistics | Description |
|---|---|
| Used Memory | Shows the amount of memory currently allocated by the running process. As Java is a language utilizing garbage collection, this number may very well get close to the maximum memory limit without being a problem for the running process. However, if the amount of used memory is close to the maximum limit for a long time, the process needs more memory. This value is displayed in bytes. |
| Maximum Memory | Shows the amount of memory that the process can use. This value is displayed in bytes. |
| Process CPU Time | Shows the percentage of CPU time that has been used. |
| Open File Descriptors | This is a Unix measurement that enables you to create a statistical diagram over the number of open files during the last minute, hour, or day. |
| Garbage Collection Count | Shows the number of times the garbage collector has run since the last time statistics was collected. |
| Garbage Collection Time | Shows the amount of time the garbage collector has run since the last time statistics was collected. This value is displayed in milliseconds |
| Thread Count | Shows the number of allocated threads. |
Workflow Statistics
collects statistical data that is sampled every 5 seconds as long as a workflow is being executed. This information includes:
| Statistics | Description |
|---|---|
| Throughput | Displays workflow throughput. As long as a workflow is being executed, |
| Queue Throughput | Displays queue throughput per second for real-time queues. Statistics for real-time queues is only available when routing UDRs, not raw data. Note! To enable its convenient delegation to external systems, or to generate an alarm if the throughput falls too low, throughput is also defined as a MIM value for the workflow. For further information, see Throughput Calculation in Workflow Properties Execution Tab (3.0). |
| Simultaneous | Displays the number of simultaneously running workflows. |
| Queue Size | The size of the queue space that is being used at the time of the sample for each individual queue. |
uses Java Management Extensions (JMX) to monitor MIM tree attributes in running workflows. For more information, refer to /wiki/spaces/UEPE3D/pages/1909507.
Viewing the System Statistics
To open the System Statistics, click the button in the upper left part of the Desktop window, and then select from the menu.
To display statistics in System Statistics, you will have to use the Search function, see the section below, Searching the System Statistics. If you want to Import statistics that was exported from System Statistics at a different time or different instance, see the section below, Importing Statistics.
Searching the System Statistics
To search, click on the Search button to open the Search System Statistics dialog.
In the Search System Statistics dialog, the search criteria must be defined in order to single out the statistics of your interest.
| Item | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
View Mode | Specifies the type of statistics you want to view; host, pico instance or workflow. | ||||||||
Resolution | Specifies the time resolution to be used. There are three different time resolutions on which statistics are collected.
| ||||||||
Criteria | The Criteria settings are used for selecting which search criteria you want the displayed statistics to meet. The following criteria are available: Host - If this option is selected, the statistics originating from the host selected in the drop-down list will be displayed. Pico Instance - If this option is selected, the statistics originating from the pico instance selected in the drop-down list will be displayed. Workflow - If this option is selected, the statistics originating from the workflow selected in the drop-down list will be displayed. Period - If this option is selected, the statistics from the chosen time interval will be displayed. Either you can select one of the predefined time intervals; Last Hour, Today, Yesterday , This Week , Previous Week , Last 7 Days , This Month, or Previous Month , or you can select the option User Defined and enter the start and end date and time of your choice in the From and To fields. Note! If several criteria are enabled, an absolute match will be displayed. For instance, if Host and Workflow is specified as well as Period , only the time for which there are both workflow measures and host measures is displayed. |
Options in System Statistics
For each type of statistics you have selected to view, you will see a Value drop-down list displaying the statistical value selected for the statistical type, and one drop-down list displaying the criteria selected. If you select another statistical value or another criteria in one of these drop-down lists, the statistical data in System Statistics is updated instantly.
For each statistics type you can see:
| View | Description |
|---|---|
Host View | The statistics for each host will be displayed in a separate color. If there are several matching hosts, all may be displayed at the same time. |
Pico Instance View | The statistics for each pico instance will be displayed in a separate color. If there are several matching pico instances, all may be displayed at the same time. |
Workflow View | The statistics for each workflow will be displayed in a separate color, and if you have selected to view queue statistics, each queue will have its own color. If there are several matching workflows/queues, all may be displayed at the same time. If you select to view Queue Throughput statistics and you have more than one route with the same name in a workflow, they are displayed separately by default, and are named in the format route name (source agent name), example: r_1 (collection1). If you want to group these queues together, such as due to legacy settings, select the Ignore Route Owner check box, and the source agent is no longer displayed per route. Note! When the Ignore Route Owner check box is selected, and there is more than one route with the same name, if the statistics are displayed on hour or day resolution, the average of all routes with the same name is shown. If the statistics are displayed on minute resolution, the statistics for one of the queues with the same name is shown, and there is no rule for which queue is shown. |
At the bottom of the window, there is a scroll bar and two buttons for zooming in and out. With these, you can focus on a particular time window within the search result. The scrollbar enables you to scroll back and forth in time to see the value changes.
At the bottom right corner of the window, you have a drop-down list that is also called Value. This list contains three different types of values:
| Value Type | Description |
|---|---|
Minimum | Displays the lowest value that was sampled |
Average | Displays the average value that was sampled |
Maximum | Displays the highest value that was sampled |
Exporting Statistics
Exporting statistics may be useful for several purposes, for example if you want to share the statistical information with someone who do not have access to your system.
To export the statistics:
In System Statistics, click the Export button.
The Save dialog will open.
Browse to the directory where you want to save the file, enter a file name and click on the Save button.
The statistical information for the selected time period will be saved in *.zip format.
Hint!
The export functionality can also be used for saving statistics on a regular basis, such as for every month or every year, to use for comparison with current statistics.
Importing Statistics
The Import functionality is used for importing statistics that has previously been exported in a system. When using the Import functionality you do not have to perform a search in order to display the statistics.
Note!
An import of statistics will not affect the data in the database, it will just display a snapshot of the statistics at the time when it was exported.
To import the statistics:
In System Statistics, click the Import button.
The Open dialog will open.
Browse to the directory where the *.zip file you want to import is located, select the file and click on the Open button.
The statistical information will now be displayed in System Statistics. The same search criteria that were set in the Search System Statistics dialog when the statistics was exported will be displayed.
The date information at the top of the dialog now displays the time interval for the imported statistics, and the text Imported Statistics will also appear in red beside the date information.
Disabling Collection of Statistics
You can disable collection of statistics on the Platform. The properties are stored in the files values.yaml file, where you define the systemProperties.
| Default value: "true" When set to false, this property will disable the collection of all statistics on all hosts and sub-systems. This property act as the master switch for Pico and Workflow stats. |
mz.statistics.collect.pico | Default value: "true" When set to false, this property will disable the collection of pico statistics on all hosts and sub-systems. |
| Default value: "true" When set to false, this property will disable the collection of workflow statistics on all hosts and sub-systems. |
Note!
When you set the property mz.statistics.collect.all to false, this overrides the settings of mz.statistics.collect.pico and mz.statistics.collect.workflow.