Monitoring Minute Graphs

Viewing Minute Graphs

This section gives information about Minute frequency graph.

To view graphical data on a per-minute frequency, navigate to the Monitoring section by performing the following steps:

1. Click Menu at the upper-left corner of the Dashboard.
2. Click Monitoring.
3. The Minute page is displayed by default. If not, then click the Minute tab on the left pane.

On the Minute page dashboard, four graphs are displayed by default. These are Queue Sizes, WIS Usage, iPOS Load, and Background CPU.

Figure 63: Per Minute Graph Dashboard

Configuring Minute Graphs

This section explains how to configure additional graphs of Minute frequency by using the minute graph template.

To configure additional graphs, perform the following steps:

Procedure 

1. Click Configure Graphs in the upper-right corner.
A page titled Configured Graphs is displayed.

Figure 64: Configured Graphs

Note:
  • When you select a particular graph, configuration information of the selected graph is displayed.
  • At any point, if you want to return to the Minute page dashboard, click Return to Graph View.
2. To configure a new graph, click Add Configuration.
A Choose Graph Type dialog is displayed.

Figure 65: Minute Graph Type
3. In the Choose Graph Type dialog, select a template from the Template Graphs dropdown list. For example, select the BG Usage template graph.
Note: When you hover the mouse over the info icon, it displays the information about the different Minute graph templates that are available.
4. Click ADD.
The configuration options for the selected graph are displayed.

Figure 66: Add Configuration
5. Configure one or multiple background processes by performing the following steps:
a. Select a machine from the Machine Name dropdown menu for each background process to plot the data on the graph. You can select a specific machine or ALL Machines. For example, select ALL Machines for the BG process.
b. Next, enter the instances in the Instance field for which you require the data plotted on the graph. For multiple instances, separate each instance by a comma (,). For example, 0,1,2. All instances is indicated by 0.
You can also enter a range in this field, such as, 1-10, which includes all instances between 1 to 10 including 1 and 10. For example, enter 1, 2 in this field for the BG process.
c. Finally, choose the parameter for which the data should be obtained from the Options dropdown list. This can be CPU, Memory, Threads, and so on. You can also select all parameters. For example, select Memory in this field.
Note: If the graph template you are configuring is for a specific parameter, such as FG CPU or FG Memory, then step c is not applicable.
6. If you want to plot data for a process on different machines separately, click the Add icon to add another row of the same process. In case you want to remove a process from the list, click the Remove icon .
7. (Optional) You can also narrow down the data to be plotted by specifying a particular MBox queue. To do this, select an MBox queue from the Queues List dropdown list. If this information is not specified, the graph is plotted with data for all MBox queues, which have the configured processes listed. For example, you did not select a specific MBox queue.
8. Enter a name for your graph. For example, you name your graph as BGMonitor.
Note: The name for your graph must be unique and should not include any special characters.
9. Click Save.

On successfully configuring the graph, a Graph added Successfully message is displayed. The graph is added to the Configured Graphs list and to the dashboard.

Figure 67: Added Minute Graph

Note:
  • Click the Edit button at the upper-right corner to edit the configuration of the selected graph. After saving the edited configuration, a Graph edited successfully message is displayed.
  • If you want to delete a graph, click the Delete icon corresponding to the graph that you want to delete. On the confirmation dialog, if you click YES, REMOVE, then a Graph deleted successfully message is displayed.
10. Click Return to Graph View to go back to the dashboard and view the graph that you just added.

Figure 68: Minute Graph on Dashboard

Similarly, you can configure the following per-minute template graphs.

Per Minute Template Graphs

Graph

Description

FG CPU

You can configure this to monitor the CPU usage for foreground processes.
These foreground processes are responsible for communicating with TIBCO iProcess Workspaces and for passing any TIBCO iProcess Workspace requests, such as released work items to the background area for processing.

In addition, you can choose to add an Active Logins parameter to compare CPU usage of the processes with the number of users logged in at a given point in time.

FG Memory

You can configure this to monitor the memory usage for foreground processes.

Additionally, you can choose to add an Active Logins parameter to compare memory usage of the processes with the number of users logged in at a given point in time.

FG Threads

You can configure this to monitor the number of threads used by foreground processes.

Additionally, you can choose to add an Active Logins parameter to compare the number of threads for the processes with the number of users logged in at a given point in time.

FG Queues

You can configure this to monitor the CPU usage for foreground MBox Queues.

BG Usage

You can configure this to monitor the CPU and memory usage for background processes.
These background processes are responsible for processing message instructions received from the clients, such as releasing a step or forwarding a step.

Additionally, you can monitor processes specific to a particular MBox queue.

Queue Message Counts

You can configure this to monitor the message count for all MBox queues.

Active Logins

You can configure this to monitor the number of active logins.

Total Resources

You can configure this to monitor the CPU, memory, and thread usage for all iProcess Engine resources.

Work Item Load

You can configure this to monitor the load on the Work Item Server (WIS).

In this case, load can be defined as:

• Largest queue (lg_queuesize).
• Work items count on WIS that is processing a large number of queues (wis_most_que_items).
• Work items count on WIS that is processing a large number of work items (wis_item_sum).