Comparison between count trends
Home > Select Project > Analysis > Counts Trend Comparison
You can check the operation trend of the key metrics of the database over time and trace the performance. You can also check the database operation trend by comparing the count trends on different dates. Through the Active sessions table, you can check active sessions and identify long-running sessions.
Basic screen guide
-
If you select Base date, Comparison date, and Instance, the data is automatically applied to all widgets based on the selected items.
-
To see the meaning of the metric displayed in the widget, select next to the name or see the following.
NoteThe tooltip of the button is not supported in multiple languages.
-
To change the position with another widget, select and drag the upper part of the widget. However, the size of the widget cannot be changed.
-
The left of the Active sessions table displays the data for the Base date, and the right of the table displays the data for the Comparison date.
-
In the Active sessions table, the text colors are changed black → orange → Red, which means that the performance of the session is getting slower.
Selecting a comparison target
Select Base date and Instance, and then select Comparison date and Instance. If you hover your mouse over the chart, you can compare the data through the tooltip that appears.
-
The solid line in the graph chart displays the data for the Base date, and the dotted line displays the data for the Comparison date.
-
The items marked with (Comparison) in the tooltip are the data for the Comparison date.
-
In Database, you can select a database for comparison.
-
The colors in Database are the same in the graph chart.
Comparing the active session data
-
The time zone for data retrieval can be checked in .
-
Active session data is collected every 5 seconds. You can search data for the desired time by selecting the button that moves in 5-second increments on the table.
-
If you select or on the upper right, you can see the data in 1-minute increments. To move in increments of 5 seconds, select or .
-
In the Active sessions table list, the text colors are changed black → orange → Red, which means that the performance of the session is getting slower.
-
If you click a specific time point of the graph chart, the () area appears with a red line and the collected active sessions can be also seen.
Comparing with a specific time
You can compare the data by zooming in on a specific time point. Select a desired time zone to anywhere on the widgets and then drag the chart. It displays the data for a specific time zone dragged to all widgets and active session tables.
Preset
In Monitoring a Database Instance, you can load the custom widget settings and the sorted active sessions as presets.
For more information about the Preset configuration, see the following.
Column information guide
- Active session
- Lock tree
- Process information
Item | Description |
---|---|
pid | Process ID |
db | Database name |
user | SQL execution account |
application | Client application name |
client_host | Host name of the connected client (reported by reverse DNS lookup of client_addr ) |
client_addr | Client IP address |
client_port | Client port number (in case of using the UNIX socket -1) |
query_hash | Hash value of query (internal WhaTap control value) |
query_start | Time when the active query started (if the state is not active, it is the last query started time) |
state | Current status of the backend process (active, idle, etc.) |
state_change | Last time when the state was changed |
xact_start | Time when the current transaction for the process started (null if no transaction is active) |
backend_start | Time when the backend process started |
backend_xmin | Minimum value of xid whose backend process is being processed |
backend_type | Type of the backend process (e.g. autovacuum worker , logical replication launcher , client backend , checkpointer ) |
backend_xid | xid whose backend is being processed |
wait_event_type | Type of the event whose backend process is in standby |
wait_event | Waiting event name where the backend process is in standby |
WhaTap basically stores the client-related information.
Item | Description |
---|---|
holder type | Type of the holder session (transaction ID, tuple, etc.) |
lock mode | holder_mode (exclusive lock, shared lock, etc.) |
waiter type | Type of the waiter session (transaction ID, tuple, etc.) |
lock request | waiter_mode (exclusive lock, shared lock, etc.) |
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 |