Monitoring Multiple Instances

Home > Select Project > Dashboard > Monitoring Multiple Instances

While you can monitor only one agent (instance) in Monitoring a Database Instance, Monitoring Multiple Instances allows you to monitor and manage multiple agents (instances).

You can compare and analyze key performance metrics occurring in each instance at a glance. You can effectively perform monitoring by aggregating data such as the number of agents running, the sum of all active sessions, and the number of transactions. Users can easily check the changes in metric values over time and high performance metrics for each instance through graph charts.

Additionally, users can see the longest-lasting active sessions, which can be used as a basis for diagnosing and resolving the system performance bottlenecks.

Multi-instance Monitoring

Tip

If you select an agent to compare in Dashboard > Instance List, and then select Multi view, the Monitoring Multiple Instances menu appears.

Viewing the past data

The dashboard basically provides real-time monitoring features in which you can view the past data.

Real-time mode	Non-real-time mode

Select in the time selector at the upper left of the screen.
Click the date and time to set the desired time zone.
Select Apply.

It updates the data in widgets placed on the dashboard based on the set time. To switch to the Realtime mode, select .

Checking the agent

Checking the agent connection status

On the upper left of the screen, the right area of the time selector provides information that allows you to check the status of agents connected to the project. This allows you to immediately check whether the target application server is running.

Total: Number of all agents connected to the project
Active: Number of active agents
Inactive: Number of inactive agents
: Can display or hide inactive agents.

Agent-based monitoring

Selecting the agent

By default, the dashboard displays the metrics collected from all agents in charts and you can also view the data by agent. Select one or more agents under the time selector. The data of the widgets on the dashboard is updated with the metrics of the selected agent(s).

Tip

To select all agents again while one or more agents is selected, deselect them or select Total.

Note

If there are numerous agents connected to the project, it is efficient to set the agent names to be short. For more information about the agent name setting, see the following.

Monitoring agents for each cluster

Agent by each cluster

If you are using Oracle Real Application Cluster (RAC), click the service name in Agent by cluster and select the Default(RAC) preset from the presets to monitor. You can check the metrics based on the instances running on the RAC database.

The widgets on the dashboard can be adjusted to the desired size and placed in the desired positions. You can also delete unnecessary widgets or add them again.

Click and hold the mouse on the Resize icon element at the lower right of the widget, and then drag it to the desired size. Grids with a uniform horizontal-to-vertical ratio appear and the size of the widget can be adjusted in each grid.

When you move the mouse cursor to the top of the widget, the cursor shape changes to Move icon . At this time, you can move the widget by dragging with your left mouse button and move to the desired position.

Right-click on a widget to delete. If you select Delete, the widget is deleted from the dashboard.

Move the mouse cursor to an empty space on the dashboard and then right-click on it. Select a widget to add from the pop-up menu. Place the widget to the desired position and then resize it.

Note

For more information about the widgets that can be placed on the dashboard, see the following.
The widgets that can be added are fixed, but we plan to increase supports through future updates.

Custom widget

The custom widget feature allows users to add their own metrics in addition to the metrics provided by default on the dashboard. If you have metrics to continuously monitor on the dashboard in addition to the metrics provided by default, use the custom widget feature.

Add

Right-click an empty space on the dashboard.
On the pop-up menu, select Add Custom Widgets.
If Custom Widget is created on the dashboard, select Select indicator.
When the Add Custom Widgets window appears on the right of the screen, enter the widget name in Title.
In the metrics list at the bottom of the screen, select the button on the upper right of the metric to add.
After the metric has been changed, select Save.

Note

You can add up to four metrics. To add metrics, select .
Ti change the metric, select a different metric in the metrics list. If you select , the metric is added.
If you do not enter the widget title, it is saved as a custom widget.

Selecting the chart type

In chart type of the Add Custom Widgets window, you can select the following types.

Series: Time series chart that displays the metric changes over time.
Equalizer: Bar graph chart that can compare the performance for multiple metrics. By visually displaying various metrics on one screen, you can easily see the overall performance status.
Pie: Pie chart useful for checking the composition ratio for multiple metrics relative to the whole.
Text: It displays the figures for the metrics in text.

Selecting the data merging method

In Merge target of the Add Custom Widgets window, you can select the way to display metrics collected from agents.

Sum: It sums up the metric values collected from multiple agents and displays them as a single value. This option is useful for displaying the overall total by merging data from multiple agents.
Avg: It averages the metric values collected from multiple agents and displays them as a single value. This option is useful for checking the average performance or status of all agents.
Max: By selecting the largest value among the metric values collected from multiple agents, it displays a single value. This option is useful for identifying the highest performance consumption or worst performance cases among agents.
No Merge: It displays the metrics for each agent.

Note

The available merge method may differ depending on the chart type.

Changing a metric

You can change or add metrics for the metrics added to the custom widget.

Select on the upper right of the custom widget added on the dashboard.
When the Add Custom Widgets window appears on the right of the screen, select a metric to change.
Select a metric to change from the metric list at the bottom of the screen. To add a metric, select on the upper right of the metric to add.
After the metric has been changed, select Save.

Tip

The features of the icon buttons in the list for added or changed metrics are as follows:

: You can exclude the metric from the custom widget.
: You can set the alert for the metric. When the button is selected, the Alert > Event Configuration appears. For more information about the Metrics event setting, see the following.

The icons displayed on the widget function as follows:

: You can see the features and information for major widgets. (multilingual support planned)
or : You can enlarge or reduce the range of the vertical axis.
: You can view the widget's data on a wider screen.
: A detail window appears where you can search the data of the widgets separately by agent.

Note

The provided options may differ depending on the widget.

Setting presets

Preset

You can save and load the settings and layouts for widgets on the dashboard. You can create a new preset by adjusting its size and placing it on the desired position.

Note

Using Default, the specified preset cannot be changed.
You can save or modify the presets with the Edit project role. For more information about the member roles, see the following.

Creating a new preset

Place the widgets in the desired format on the dashboard. You can also resize and place only the widgets to be frequently checked.
On the upper right of the screen, select .
Enter a new preset name.

To save the selected agent data, select Include agent selection history.
Select Save.

You can see the newly saved preset from the preset list.

Note

If any changes are made to the newly created preset, save the preset again. Select and then save the preset with the same name. Any changes are overwritten in the existing preset.
If you go to another menu without saving changes on the dashboard, the changes are not saved.
Presets are saved on a project basis and can be shared with other users.

Deleting presets

If you have unused presets, you can delete them from the preset list. Select on the right of the item to delete from the preset list.

Note

The Default preset cannot be deleted.

The types of widgets that can be placed on the dashboard are as follows.

XOS widgets

[XOS] CPU

You can see the CPU usages for each agent in real time.
[XOS] Memory

You can see the memory usages for each agent in real time.
[XOS] Disk Usage

Displays the disk utilizations, free sizes, and total sizes for each agent.
- : The Disk usage details pop-up window appears. You can check the chart that displays the disk usage by time zone. You can check the data by instance. By selecting Size, Free, or Used, you can see the total size, remaining size, and size in use.
- : You can expand the table on the widget to a wider screen.
Tip
If there is no data displayed, add the following settings to the xos.conf file.
xos.conf
# Off if the disk usage is 0; unit: second disk_usage_interval=60

[RAC] Load Balance

You can monitor the resources of instances running on the Oracle RAC (Real Application Clusters) database in real time. Users can visually monitor the load and performance metrics for their database. You can check the CPU performance, active sessions, physical read operations, and available memory.
[RAC] Interconnect Bandwidth

This widget monitors the interconnect bandwidth used in Oracle RAC (Real Application Clusters). You can monitor the network traffic between databases and instances within a cluster by displaying the communication bandwidth between database nodes in real time.
[RAC] Main Waits

You can see the global lock status and the numbers of waits for each event. This widget queries the total number of waits for each event through metrics collected for a specific database category and extracts the most recent data for each agent (instance). This allows you to see the database wait events promptly at a specific time.

Database widgets

Active Sessions

It visually displays the numbers of active sessions over time in a time series chart. This widget traces and graphs the numbers of sessions running in the database over time. It is useful for visually checking the session usage patterns and load.
Lock Wait Sessions

It visually displays the numbers of lock waiting sessions over time in a time series chart. This widget traces the numbers of sessions in lock waiting state in the database over time and displays it on the graph in real time.
Long Active Session Count

It provides information about active sessions running on the database for long time. A chart appears for information aggregated by time zone with grouped by the session execution time. It can identify long-running sessions with performance issues or resource leaks in the database, or classify the sessions based on the execution time to visually display which sessions stay active for long time.

It appears in blue for less than 3 seconds, green for 3 seconds or more that is less than 10, orange for 10 seconds or more that is less than 15, and red for 15 seconds or more.
Long Waiting Session Count

It provides information about the long-term latency of the sessions holding or waiting for locks in the database. By combining lock information and active session information, you can trace long-term latencies for queued sessions. It monitors the sessions that are holding locks or waiting for long time. You can visually see which sessions are holding locks or waiting for long time.

It appears in blue for less than 5 seconds, green for 5 seconds or more that is less than 10, orange for 10 seconds or more that is less than 60, and red for 60 seconds or more.
SQL Elapse Map

Displays a real-time chart for the elapsed times of running queries. If you drag a specific part of the chart, the Query List appears. You can enlarge or reduce the range of the vertical axis by selecting or .

Note
The execution times of queries are calculated after collecting active sessions. Therefore, depending on the active session collection cycle, there may be a margin of error. See the following figure. The execution times of SQL queries that have ended within the collection cycle are not calculated. A shorter collection cycle may decrease the margin of error, but considering the database load, it is typically set to 5 seconds. It is useful for monitoring long-running queries. The same is true for the data in SQL statistics.

Wait Event

It displays a real-time graph for the names of the waiting events that each backend process is waiting on, along with the frequency with which those events occurred. It mainly monitors waiting events related to application, configuration, administrative, network, and the like. You can visually see the frequency of each waiting event. If you hover your mouse over the graph, a tooltip is displayed providing more information about each waiting event.
Physical Reads

This widget monitors physical reads occurring in the database. It monitors the I/O performance of the database, by providing statistics on the operations where the database reads data from the disk.
Excute Count

This widget monitors the numbers of queries or procedures executed in the database. It traces the numbers of queries or procedures executed by the database in real time and provides them to the user.
Session Logical Reads

This widget monitors logical reads executed in the database session. It traces and provides real-time visibility to users on the number of logical read operations executed in the database session.

You can view real-time active sessions and lock trees in the Session Table widget at the bottom of the screen.

Active sessions: You can view active sessions and queries.
- If you select a session running, the Session detail window appears. You can see the details for the selected session. For more information, see the following.
- If you select an item in the rightmost query_text column in the table, the SQL details window appears. You can see the full text and plan information for the selected query. For more information, see the following.

Lock tree
You can see the lock session information, and holder and waiter information in real time. For more information about the table columns, see the following.

Note

In the table list, the text colors are changed black → orange → Red, which means that the performance of the session is getting slower.

Checking the session information details

If you select a session in the Active sessions tab, the Session detail window appears. You can see the information details about the selected session.

Session detail

The session information is viewed in real time by default. If you select in the time selector, you can stop a real-time view and see the data based on the paused time. To refresh data while pausing a real-time view, select .
Kill Session: You can stop the selected session. If the Session kill window appears, enter the password (Parameter Key) and then select Apply.

Note
This feature is only available in real-time viewing mode.

Session history: You can go to the Session History menu to see the records of the selected session.

Note
For more information about Session History, see the following.

Session Stat: It provides various performance metrics and statistical information for the selected session. It includes the type and number of tasks performed in the session, resource usage, and more.
Delta / Sigma: The change rate and statistical analysis information for the selected session appear. You can check the amount of change in session activities.

Session Info: You can see the basic information of the selected session and the information details including the status.
Wait Info: The waiting event and waiting time of the selected session are provided. You can also see information about the waiting events that occur when the database system is waiting to execute a specific task.
SQL Text / Plan: You can see the SQL query statements and plans of the selected session. For more information, see the following.

See query details

To check the SQL query information of the executing session, select the query (or sql_text) column in the Active sessions section. The SQL details window appears. You can check the SQL query statements and plan information.

SQL details

View SQL Statistics: You can go to the SQL statistics menu where you can check statistical information related to the SQL query statement.

Runtime Plan: It provides the execution plan and runtime information for a selected SQL query. It provides the information details such as execution count, average execution time, and average physical reads.
Explain Plan: It displays the execution plan predicted by the optimizer. It provides information such as cost, job, object name, and cardinality.
Plan History: You can check the history of the execution plans of the SQL queries executed in the database.
Bind Capture: You can see the values of the bind variables used in SQL queries executed in the database. This allows you to see actual content of query executions.

Note
This is a value captured in the database (v$sql_bind_capture), not a bind value executed in real time. If the number of cases is too large, it displays up to 100.

Filtering the table data

Filter

Select on the upper right of the table.
Select a column header and a condition in the table.
Enter a desired value in the Enter conditions field.
Select Save.

Setting the table columns

You can hide the table header columns or add any of them. You can also change the column order. Select .

Column Settings

Note

After configuration, select Confirm to apply the settings in the table.
In the search bar, enter text to search the desired columns. Only the columns that meet the entered text are displayed.
Images may differ depending on the product, project, or menu.

Adding columns

From the list, select the items to add as table header columns. To select all items, select Select All.

Deleting columns

From the list, unselect the columns to delete. Alternatively, select on the right of the item to delete from the list.

Changing the column order

Drag an item to reposition from the list, and then move it to the desired position.

Initializing the configuration

To cancel all changes and reset them, select Initialized.

Column information guide

For more information about columns, see the link.

Item	Description
`sid`	Session ID
`cpu(xos)`	CPU utilization collected by the installed XOS
`serial#`	Value to increment to determine if the same session ID has been used.
`username`	DB user name.
`command`	Same as `COMMAND_TYPE`; SQL command number
`status`	Session status
`schemaname`	Schema. Same as the username.
`osuser`	Username of the OS that accessed the session.
`spid`	OS process ID.
`process`	ID of the client process that accessed the session.
`logon_time`	Session created time point.
`last_call_et`	If the session is active, it is the elapsed time (sec) since activation.
`sql_text`	`query`, running statement, SQL statement that separates literal strings
`sql_param`	Literal value separated from `query`
`prev_sql_text`	Previously executed query
`prev_sql_param`	Previously executed query param
`program`	Program information executed by client
`type`	session type - can be adjusted in user background recursive (whatap.conf).
`seq#`	Number that uniquely identifies the current or last wait (incremented with each wait)
`event`	Number of the resource or event if the session is waiting.
`p1`	First waiting event parameter (decimal point)
`p2`	Second waiting event parameter (decimal point)
`p3`	Third waiting event parameter (decimal point)
`wait_class`	Class name of the waiting event
`wait_time`	The value is `0` if the session is waiting. It is the last waiting time (milliseconds) if the value is greater than `0`.
`seconds_in_wait`	Time spent waiting for the wait if the session is waiting. Otherwise, it is the time elapsed since the last waiting.
`state`	Waiting state: `WAITING`, `WAITED UNKNOWN TIME`, `WAITED SHORT TIME`, `WAITED KNOWN TIME`
`machine`	Name of the client server that accessed the session (hostname)
`port`	Clinet port number
`terminal`	Client terminal name
`module`	Name of the module set by the user of the program executed on the client.
`action`	Action name set by the user of the running module.
`client_info`	Client information set by user
`client_identifier`	Client ID set by user
session logical reads	Number of times data was read into the buffer cache
physical reads	Number of data reads from the physical disk
execute count	SQL execution count
parse count (hard)	Total number of syntax analysis calls (actual syntax analysis)
parse count (total)	Total number of syntax analysis calls (hard, soft, describe)
opened cursors current	Number of open cursors
db block changes	Change count of all blocks in the database
session pga memory	Session's current PGA size
`undo_segid`	Undo information ID
`undo_blk`	Undo block count
`undo_rec`	Undo record count
`sql_address`	SQL statement identification data
`sql_hash_value`	SQL statement identification data
`sql_id`	SQL ID of the running SQL statement
`sql_child_number`	Sub number of the running SQL statement
`sql_exec_start`	Start time point of SQL running in the session
`sql_exec_id`	SQL running ID
`prev_sql_addr`	Information that identifies the last run SQL statement
`prev_child_number`	Sub number of the last SQL statement executed
`prev_exec_start`	Start time point of the last SQL statement executed
`prev_exec_id`	Start ID of the last SQL statement executed
`plsql_entry_object_id`	Object ID of the top PL/SQL subprogram on the stack.
`plsql_entry_subprogram_id`	ID of the top PL/SQL subprogram on the stack.
`plsql_object_id`	Subprogram ID of the running PL/SQL object
`taddr`	Transaction address
`lockwait`	lock wait address (lock address where the session is waiting)
`row_wait_obj`	Object ID of the table containing the row specified in `ROW_WAIT_ROW#`
`row_wait_file`	ID of the data file containing the row specified in `ROW_WAIT_ROW#`
`row_wait_block`	ID of the block containing the row specified in `ROW_WAIT_ROW#`
`row_wait_row`	Currently locked row
`pdml_status`	If the value is `ENABLED`, the session is in `PARALLEL DML` activation mode. If the value is `DISABLED`, the session does not support the `PARALLEL DML` activation mode. If the value is `DISABLED`, the session does not support the `PARALLEL DML` activation mode.
`pq_status`	If the value is `ENABLED`, the session is in `PARALLEL QUERY` activation mode. If the value is `DISABLE`, the session does not support the `PARALLEL QUERY` activation mode. If the value is `FORCED`, it indicates the session was changed to force the use of `PARALLEL QUERY`.
`blocking_session_status`	It provides details about whether there is a blocking session.
`blocking_instance`	Instance ID for the blocking session
`blocking_session`	Session ID for the blocking session
`final_blocking_session_status`	It provides details about whether there is a last block session.
`final_blocking_instance`	Instance ID for the last blocking session
`final_blocking_session`	Session ID for the last blocking session
`service_name`	Service name of the session. It is similar to the DB name.
`saddr`	Session address
`con_id`	ID of the container associated with the data (only for multi-database support)
`rss(xos)`	OS metrics collected by the XOS agent
`pss(xos)`	OS metrics collected by the XOS agent
`ioread(xos)`	OS metrics collected by the XOS agent
`iowrite(xos)`	OS metrics collected by the XOS agent

Note

WhaTap basically stores the client-related information.

Downloading the view list

You can download the current Session Table list in CSV format. Select on the upper right of the Session Table section.

The naming format of the downloaded file is as follows:

Active sessions: activeSession_HH_MM_SS.csv
Lock tree: lockTree_HH_MM_SS.csv

Viewing in a new window

You can see the Session Table list on a new wider screen. Select on the upper right of the Session Table section.

Monitoring Multiple Instances

Viewing the past data