Working with Monitors
This chapter is intended to teach the basic usage of monitors and introduce the default system monitors provided with Altibase.
Usage
Open/Close Monitors
- Open monitor: Choose a monitor item on the left tree menu and click it. The result view will show up in the right panel.
- Close monitor: To close a monitor, click the 'X' icon at the top of the open monitor result screen.
Upon disconnection from a database, all open monitor result screens for the database will be closed automatically.
System Monitors
When connected to a database after creating the database connection, several folders and items will be shown,
as in the following picture. The first folder, "Monitors", contains "User Monitors" and "System Monitors".
"User Monitors" is the place for containing user-defined monitors.
DBAs can create their own monitors by importing monitors written in XML format.
The "System Monitors" folder, the main focus of this section, contains the ready-made monitors provided with Altibase. If a monitor title has "History" at its end, it is a kind of history monitor. Otherwise, it is a snapshot monitor.
The monitors in "System Monitors" are organized as follows. (The monitors may vary depending on the version of AdminCenter for DBA.)
- Overview: The overall state of the database at the moment.
- DB Properties: The current list of Altibase property name/value pairs.
- Space: Memory and Disk-related monitors
- DB Memory Usage: The current memory consumption by Altibase modules.
- Tablespaces: Disk The current disk usage by tablespaces and their dependent datafiles.
- DB Memory History: The history of Altibase module memory usage.
- Tablespaces History: The history of disk usage for tablespaces and their dependent datafiles
- Workload: DB client-related monitors.
- Workload Overview: The overall DB state related to clients.
- Session Statistics: Statistical information on client connections.
- Sessions and Statements: Detailed information on connections and SQL statements.
- Long-run queries: Long-running SQL queries and Table full scan queries that may degrade the performance of the DB.
- Wait Events: Statistical information pertaining to waiting events in the DB.
- Session Timeout History: The history of client session timeout events.
- Session List History: The history of session details.
- Statement List History: The history of statements issued by clients.
- Long-run Queries History: The history of long-running Update statements issued by clients.
- Long-run Update History: The history of long-running Update statements issued by clients.
- Table Full Scan Queries History: The history of client queries that performed table full-scanning.
- Wait Event History: The history of waiting events in the DB.
- Resource Contention: Contention due to limited DB resource
- Buffer: The current disk DB-related buffer state.
- Lock: The current lock contention on DB objects.
- Buffer History: The history for buffer state changes.
- Lock History: The history of lock contention.
- System: OS state monitors (Available only when AMOND is running)
- CPU and Memory: CPU and memory usage by the OS.
- Disk Usage of ALTIBASE: Analysis on disk usage by files related to Altibase.
- CPU History: The history of CPU usage.
- Memory History: The history of Memory usage.
- ALTIBASE Memory Usage History: The history of Altibase memory consumption, expressed as a proportion of that of the OS.
- Swap History: The history of Swap usage.
- Memroy-DB Disk Usage History: The history of disk usage by the Memory DB file.
- Disk-DB Disk Usage History: History for disk usage of Disk DB files.
- DB Log Disk Usage History: History for disk usage of DB log.
- DB Archive Disk Usage History: The history of disk usage by DB archive files.
Limitation
DBAs should keep in mind that having too many monitors open can consume all of the Java heap space on the client computer.