Monitoring Multiple Instances

Info

This document has been created based on the Altibase Monitoring V2. For the Altibase monitoring V1 document, see the following.

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.

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

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.

Preset

Default: This preset consists of XOS metrics, AWS RDS CloudWatch metrics, and major DB metrics.
Default(xos): This preset consists of XOS metrics and major DB metrics.
Default(rds): This preset consists of AWS RDS CloudWatch metrics and major DB metrics.

Note

The default preset (Default) cannot be changed.

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

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.

Logical Reads (data page gets)

Number of cases a data page has been accessed using a latch in the system or session. The hit ratio of a buffer is calculated as (get pages + fix pages - read pages) / (get pages + fix pages).
Physical Reads (data page read)

Number of cases a page is read from the system or session, which is a physical read count where a page that is not loaded into the buffer is read from disk. A high number of physical reads can slow down the system's query processing speed.
Memory Table Access (memory table access count)

Number of cases a memory table has been accessed by the system or session.
Disk Table Full Scan (disk table cursor full scan count)

Number of cases a full scan cursor on the disk table has been opened in the system or session.
Commits (session commit)

Number of commits occurred in the system or session.
Undo Reads (undo page gets)

Number of cases an undo page has been accessed using a latch in the system or session.
Execute Count (execute success count)

Number of cases a query has been successfully executed in the system or session. To evaluate the transaction throughput, you can calculate it as execute success count + prepare success count + prepare failure count.
Prepare Count (prepare success count)

Number of cases the Prepare step succeeded in the system or session. This step includes checking for query syntax errors and establishing an execution plan, and can account for 60-70% of the overall query processing time. If this value is too high, query optimization is required to reduce repetitive Prepare operations.

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 an item in the rightmost query 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.

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.

Default Bind: You can bind the part set as a variable in the query sentence to the default value.
Reset Bind: You can release the bound default value and check the variable.
Formatting: You can improve readability by applying indentation and formatting to a SQL query statement.

Plan: To check plan information, enter DB Name, User Name, and Password, and then select .

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.

Active session
Lock tree
Process information

Item	Description
`action`	Task or command running in the current session.
`active_flag`	Whether the session is active or not.
`autocommit_flag`	Whether automatic commit is active or not.
`client_app_info`	Information about the client application.
`client_info`	Custom information of the client.
`client_nls`	Client's National Language Support (NLS) setting.
`client_package_version`	Version of the client package.
`client_pid`	Process ID of the client.
`client_protocol_version`	Version of the protocol used between the client and server.
`client_type`	Client type.
`comm_name`	Name of the communication being used in the session.
`commit_write_wait_mode`	Data write waiting mode upon commit.
`current_stmt_id`	ID of the SQL statement running.
`data page gets`	Number of accesses to read the data page.
`data page read`	Number of physical reads to the data page.
`db_username`	User name connected to the database.
`dblink_global_transaction_level`	Global transaction level of the DB link.
`dblink_remote_statement_autocommit`	Whether the DB link remote document is automatically committed or not.
`dbname`	Name of the connected database.
`ddl_time_limit`	Time limit for DDL (Data Definition Language) operations.
`default_date_format`	Default date format.
`default_tbsid`	Default tablespace ID of the session.
`default_temp_tbsid`	Default temporary tablespace ID of the session.
`elapse_time`	Time elapsed since the task started.
`event`	Current or last event occurred.
`execute success count`	Number of successful commands executed.
`failover_source`	Source server information upon failover.
`fetch_time_limit`	Maximum time to fetch data.
`header_display_mode`	Display mode of the header information.
`id`	Unique ID of the session.
`idle_time_limit`	Idle time limit of the session.
`isolation_level`	Isolation level of the current transaction.
`lob_cache_threshold`	Threshold of the LOB (Large Object) cache.
`login_time`	Login time of the session.
`max_statements_per_session`	Maximum number of statements that can be executed per session.
`memory table access count`	Number of accesses to the memory table.
`module`	Name of the running module.
`nls_currency`	Currency symbol used in NLS settings.
`nls_iso_currency`	ISO currency code used in NLS settings.
`nls_numeric_characters`	Numeric characters used in NLS settings.
`nls_territory`	Regional information used in NLS settings.
`oname`	Agent or instance name.
`opened_stmt_count`	Number of open SQL statements.
`optimizer_mode`	Query optimization mode.
`p1`	First parameter of the event.
`p2`	Second parameter of the event.
`p3`	Third parameter of the event.
`paralle_dml_mode`	Parallel DML (Data Manipulation Language) mode.
`query`	Executed SQL query.
`query_hash`	Hash value of the query.
`query_param`	Parameters used for a query.
`query_rewrite_enable`	Whether to enable the query rewrite operation or not.
`query_time_limit`	Time limit for query operation.
`rebuild count`	Number of rebuild operations.
`replication_mode`	Replication mode setting.
`second_in_time`	It represents the time in seconds.
`seqnum`	Sequence number of the session.
`session_state`	Current state of the session.
`ssl_certificate_issuer`	Issuer of the SSL certificate.
`ssl_certificate_subject`	Subject information of the SSL certificate.
`ssl_cipher`	SSL encryption method in use.
`stack_size`	Stack size of the session.
`sysdba_flag`	It represents whether to use the SYSDBA role or not.
`task_state`	Current task state.
`time`	Task operation time.
`time_zone`	Time zone setting for the session.
`trans_id`	Current transaction ID.
`transaction_mode`	Transaction mode.
`trx_update_max_logsize`	Maximum log size during transaction update.
`utrans_time_limit`	Time limit for user transactions.
`wait_time`	Waiting time of the session.
`xa_associate_flag`	XA transaction associated flag.
`xa_session_flag`	XA transaction session flag.

Item	Description
`oname`	Agent or instance name.
`id`	Unique ID of the session.
`db_username`	User name connected to the database.
`elapse_time`	Time elapsed since the task started.
`waiter type`	Type of the entity waiting for a lock.
`holder type`	Type of the entity holding a lock.
`holder desc`	Detailed description of the entity holding a lock.
`waiter desc`	Detailed description of the entity waiting for a lock.
`query`	Executed SQL query.
`query_param`	Parameters used for a query.

The following items are the metrics collected if the XOS agent has been installed.

Item	Description
`cputime`	CPU usage time
`cpuusage`	CPU Utilization
`elapse`	Elapsed time of CPU usage
`vsize`	Virtual memory size (Kb)
`rss`	Resident Set Size (RSS) that is the number of physical pages associated with the process.
`state`	Process status
`ioread`	Actual time spent reading the block (milliseconds)
`iowrite`	Actual time spent writing the block (milliseconds)
`pss`	Process specific memory usage + Percentage of shared memory occupied by one process
`uid`	user id
`cmd`	Executing command
`longcmd`	Full path of cmd

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