Monitoring Multiple Instances
Home > Select Project > Dashboard > Multiple Instance Monitoring
In Instance Monitoring, to monitor only one instance, Multiple Instance Monitoring allows you to check and compare metrics and active sessions of multiple instances on one screen. Graph charts make it easy to see how instances' metric values are trending and which instances have higher metric values.
If you select an agent to compare in Dashboard > Instance List, and then select Multi view, the Monitoring Multiple Instances menu appears.
Basic screen guide
-
Instance
It is a list of instances (databases) where the agent has been installed. The color of the instance matches the color of the graph chart placed on the screen. To exclude some instances of data from the graph chart, select the corresponding instances. If you select the instance again, the graph chart reflects the instance data.
-
Status
You can monitor the metrics related to the resources of your database server.
-
Load balance
You can monitor whether the load is concentrated on one server by checking which instance has a high metric value.
-
Graph chart section
The horizontal axis of each widget is time, and the vertical axis is the metric number.
-
Active sessions | Lock tree
You can view information such as active session, and lock tree for a specific instance. Select the Instance Name button.
-
For more information about each metric, see the following.
-
For more information about the columns, see the following.
Selecting a metric
You can change the metric of the graph chart widget placed on the screen to another one.
-
Select on the upper right of the widget to change the metrics.
-
If the Count selector window appears, select a desired metric.
-
Select Save.
The metric of the selected widget is changed.
For more information about each metric, see the following.
Layout setting
To set the layout on the metrics chart, on the upper right of the screen, select . Nine (3x3) metrics charts are set on the default layout, and you can change the number of charts on a page.
Using the active session section
Through Active sessions at the bottom of the screen, you can see the real-time active sessions. The following provides the guide for the button on the upper right of the table.
- : You can stop changing the data collected in real time. To restart it again, select .
-
: The list of tables is refreshed.
-
: The column header entries in the table can be displayed or hidden.
-
: You can filter the list based on the column header entries in the table. After selecting the button, you can set the conditions in each header column such as Includes, Excludes, Equal, and Unequal.
NoteAdjust the column width if the text field for filter condition options is invisible.
-
: You can download the content of the table as a CSV file.
Stopping an active session
You can stop a session(s) that has been running for a long time.
-
In the Active sessions list, move your mouse cursor to the session to terminate.
-
Select the that appears on the utmost right.
-
If the Session kill window appears, enter the password.
-
Select Apply.
The session is stopped.
-
Through the paramkey.txt file in the DBX agent installation path, you can find the password.
-
This feature is only available to the members with Edit role. For more information about member roles, 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.
- View SQL Statistics: You can go to the SQL statistics menu where you can check statistical information related to the SQL query statement.
Changing the table columns
You can display or hide the column entries in the table, and change their order.
-
Select on the upper right of the table.
-
When the Column Setting window appears, hide, add, or change the order of items to be displayed in the table columns.
- Select a column, and then , , or . Go to Visible or Invisible.
- You can move the position by dragging the column while it is selected.
-
After all settings are finished, select Save.
The setting is saved as a browser cookie value to maintain the state even after refreshing the page. If an error occurs between settings due to cookie deletion or other reasons, it is initialized.
Column information guide
For more information about columns, see the link.
- Active session
- Lock tree
- Process information
Item | Description |
---|---|
application | Name of the application that created the session. |
blocking_session_id | ID of the session that is blocking the current session. |
client | Name or IP address of the client that created the session. |
command | SQL command on which the session is running. (SELECT, INSERT, UPDATE, DELETE) |
completion_time | Time when the SQL operation is expected to finish. |
cpu(%) | The rate of the CPU used by the session. |
cpu_time | Amount of CPU time (milliseconds) used in the session. |
cpu_time(sigma) | Total CPU time used in all sessions. |
db | Name of the database to which the session is connected. |
elapsed_time | Elapsed time (milliseconds) since the session started. |
granted_query_memory | Amount of memory (pages) allocated for query execution. |
host | Name of the client host that created the session. |
isolation | Transaction isolation level of the current session. |
last_request_start_time | Time when the last request in the session started. |
last_wait_type | Last type that the session waited for. |
login_time | Time when the session logged into SQL Server. |
logical_reads | Number of logical reads that occurred in the session. |
logical_reads(sigma) | Total number of logical reads that occurred across all sessions. |
memory_usage | Amount of memory the session uses. |
object | Name of the database object referenced by the running SQL statement. |
objectid | ID of the object running in the session. |
percent_complete | Completion rate of the executing command. |
plan_handle | Handle that identifies the SQL plan. |
reads | Number of physical reads that occurred in the session. |
reads(sigma) | Total number of physical reads that occurred across all sessions. |
row_count | Number of rows processed in the session. |
sql_hash | Hash value of the SQL statement running in the session. |
sql_param | Parameter value of the SQL statement running in the session. |
sql_text | Entire text of the SQL statement running in the session. |
status | Current state of the session. e.g. running , suspended , etc. |
wait_resource | Resource the session is waiting on. |
wait_time | Time (milliseconds) that the session has been waiting. |
wait_type | Type of wait the session is waiting on. |
writes | Number of physical writes that occurred in the session. |
writes(sigma) | Total number of physical writes that occurred across all sessions. |
Item | Description |
---|---|
application | Name of the application that created the session. |
client | Name or IP address of the client that created the session. |
db | Name of the database to which the session is connected. |
elapsed_time | Elapsed time (milliseconds) since the session started. It is used to measure how much time has passed since a lock occurred. |
host | Name of the client host that created the session. |
id | Unique ID for the locked session. |
last_wait_type | Last type that the session waited for. |
row_count | Number of rows processed in the session. |
sql_param | Parameter value of the SQL statement running in the session. |
sql_text | Entire text of the SQL statement running in the session. |
status | Current status of the session. For example, there are running , suspended , sleeping , and such which indicate whether the session is active or waiting. |
user | Name of the user connected to SQL Server. |
wait_resource | It indicates the resource the session is waiting for. |
wait_time | Time (milliseconds) that the session has been waiting. |
wait_type | Type of wait the session is in. For example, it includes information such as lock wait or IO wait. |
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 |
WhaTap basically stores the client-related information.