Chart Descriptions
This is a list of most charts in Database Performance Monitor with their title, unique ID, and a brief description.
Jump to:
MongoDB Charts
| Chart Title | Chart ID | Chart Description |
|---|---|---|
| MongoDB Asserts | mongo-asserts | Asserts are errors in MongoDB; a large number usually indicates an application problem. |
| MongoDB Time Since Last Flush | mongo-backflushing-last | The timestamp of the last completed flush operation in the ISODate format. If this value is more than a few minutes past your server’s current time and accounting for differences in time zone, restarting the database may result in some data loss. Also consider ongoing operations that might skew this value by routinely blocking write operations. |
| MongoDB Intra-Cluster Connection Pool | mongo-connection-pool | Shows the connection activity between the selected server and other members of its sharded cluster, over time. For Mongos, this measurement provides context on the number of active requests to the cluster. |
| MongoDB Connections | mongo-connections | Connections indicate the total number of clients on the server. Most clients use connection pooling, so if you see a high number of connections your application connection pool may be too large. |
| MongoDB Page Faults | mongo-extra-page-faults | Shows page faults over time for the server; high page faults may relate to poor performance and can indicate your working set does not fit in memory. |
| MongoDB Active Clients | mongo-global-lock-active-clients | Shows clients actively running or waiting on a lock to run; too many active or queued clients may indicate that your server does not have enough resources for its workload. |
| MongoDB Query Latency Bands | mongo-latency-bands | Shows a count of query executions within different latency bands. An increase in executions jumping to higher bands may indicate a stall in the server. |
| MongoDB Memory Usage | mongo-mem | Shows memory consumption in the server; if using MMAPv1 “mem.mapped” reports how much actual data is mapped into memory. |
| MongoDB Open Cursors | mongo-metrics-cursor-open | Shows cursor activity in the server over time. A large number of open or timed_out cursors may be a sign of an application error. |
| MongoDB Document Operations | mongo-metrics-document | Shows document-level activity in the server over time; spikes should be investigated to make sure the database is not overloaded. |
| MongoDB getLastError Waits | mongo-metrics-lasterr-count | The total number of getLastError operations with a specified write concern (i.e. w) that wait for one or more members of a replica set to acknowledge the write operation (i.e. a w value greater than 1.) |
| MongoDB getLastError Timeouts | mongo-metrics-lasterr-tout | The number of times that write concern operations have timed out as a result of the wtimeout threshold to getLastError. |
| MongoDB getLastError Total Wait Time | mongo-metrics-lasterr-wait | The total amount of time in milliseconds that the mongod has spent performing getLastError operations with write concern (i.e. w) that wait for one or more members of a replica set to acknowledge the write operation (i.e. a w value greater than 1.) |
| MongoDB Record Moves | mongo-metrics-record-moves | When using MMAPv1 shows the number of documents that were re-written because they exceeded their allocated record-size. If you see high activity here you may want to review the record-allocation strategy configured for your server. |
| MongoDB Scanned Items | mongo-metrics-scanned-items | Shows the number of scanned index entries and document objects as well as the number of operations that could not use and index for sorting. A high ratio of scanned_objects/scanned may indicate that your indexes are not effective for your working set. |
| MongoDB Deletes From TTL Indexes | mongo-metrics-ttl-deletes | The total number of documents deleted from collections with a ttl index. |
| MongoDB Passes For TTL Deletes | mongo-metrics-ttl-passes | The number of times the background process removes documents from collections with a ttl index. |
| MongoDB Request Count | mongo-network-requests | The total number of distinct requests that the server has received. Use this value to provide context for the network.bytesIn and network.bytesOut values to ensure that MongoDB’s network utilization is consistent with expectations and application use. |
| MongoDB Network Use | mongo-network | The number of bytes of network traffic sent and received by this database. Use these values to ensure that network traffic sent to the mongod process is consistent with expectations and overall inter-application traffic. |
| MongoDB Operations | mongo-op-counters | Shows command-level activity in the server over time. Similar to “Document Operations” but be aware that a single command can generate activity on multiple separate documents. |
| MongoDB Oplog Window | mongo-oplog-window | The time difference between the first and last operations in the oplog. If a secondary is down longer than the oplog window it will require a full sync. |
| MongoDB Query Latency | mongo-query-latency | Shows the average time for a given query to complete; spikes may indicate a general slowdown or they may indicate more extreme slowdowns in a few areas of your server workload. Consult your Query Latency Bands to determine which is the case. |
| MongoDB Replica Lag | mongo-repl-delay | The optime difference between the slave and primary. Excessive lag makes members ineligible to quickly become the primary and increases the possibility that distributed read operations will be inconsistent. |
| MongoDB Replica Headroom | mongo-repl-headroom | The difference between the primary\’s oplog window and the replica lag of the secondary. If this value goes negative, write operations will be overwritten before secondaries have a chance to replicate them requiring a full sync. |
| MongoDB WiredTiger Cache Activity | mongo-wt-cache-activity | Shows how often data is read into/written from the WiredTiger cache. High cache activity may indicate that your server needs more memory; check for disk activity to see if your working set does not fit in memory. |
| MongoDB WiredTiger Cache Bytes | mongo-wt-cache-bytes | Shows memory usage of the WiredTiger internal cache. |
| MongoDB WiredTiger Cache Page Eviction | mongo-wt-cache-page-eviction | Show statistics on pages evicted from the cache over time. If you have high unmodified page evictions coupled with spikes in disk read activity it may indicate your working set is too large to fit in memory. |
| MongoDB WiredTiger Concurrent Transactions | mongo-wt-conc-transactions | Shows statistics on active and available concurrent operations. Consistently high active operations may indicate that the server cannot keep up with your workload. |
| MongoDB WiredTiger Connection I/Os | mongo-wt-connection-ios | Shows statistics on read/write operations made over time. These provide a good overview of storage-engine level activity and include operations against memory as well as disk. |
| MongoDB WiredTiger Transaction Checkpoint Times | mongo-wt-transaction-checkpoint-time | Shows statistics on the time it takes to execute checkpoints in the storage engine; increases in checkpoint time may indicate an I/O bottleneck in the server. |
MySQL Charts
| Chart Title | Chart ID | Chart Description |
|---|---|---|
| MySQL Rows Affected | machine-mysql-handler-rows-affected | Number of rows affected by inserts, updates, or deletes. |
| MySQL Threads Connected | machine-mysql-threads-connected | Number of threads connected, regardless of what they are doing. |
| MySQL Threads Running | machine-mysql-threads-running | Number of threads actively running, i.e. not sleeping. |
| Slow Queries Throughput | machine-slow-queries | Rate of queries executed that are considered “slow,” i.e. longer than the long_query_time or log_min_duration_statement. |
| MySQL Aurora Replication | mysql-aurora-replication | Replication lag for Aurora hosts, expressed as min, max, and average. |
| MySQL Authentication Failures | mysql-auth-failures | Number of authentication failures, whether from blocked hosts, access denied errors, or other failures. |
| MySQL Connection Latency | mysql-connection-latency | Average amount of time it takes the database to accept a new connection. |
| MySQL InnoDB Adaptive Hash Index | mysql-innodb-adaptive-hash-index | Activity against the adaptive hash index. A high number of searches and activity usually indicates the index is effective. |
| MySQL InnoDB Buffer Pool and Memory | mysql-innodb-bp-and-mem | Pending IO operations within InnoDB. A large number of pending operations usually indicates an IO bottleneck. |
| MySQL InnoDB Buffer Pool Cache Miss Ratio | mysql-innodb-buffer-pool-cache-miss-ratio | Percentage of operations that cannot be satisfied by data in the buffer pool. If this is high, the buffer pool may be too small. |
| MySQL InnoDB Buffer Pool Read-Ahead | mysql-innodb-buffer-pool-read-ahead | Pages read into and evicted from InnoDB buffer pool. Consistent read-ahead evicted activity indicates this may not be helpful for your workload. |
| MySQL InnoDB Buffer Pool Read-Write Requests | mysql-innodb-buffer-pool-read-write-requests | Number of requests to the InnoDB buffer pool by reads and writes. Spikes indicate the data is reading or writing a lot of data at once; for example, when a query is possibly examining too many rows. |
| MySQL InnoDB Buffer Pool Reads | mysql-innodb-buffer-pool-reads | Number of logical reads that InnoDB could not satisfy from the buffer pool, and had to read directly from disk. |
| MySQL InnoDB Buffer Pool | mysql-innodb-buffer-pool | Amount of data in the buffer pool in each state. |
| MySQL InnoDB Current Operations | mysql-innodb-cur-ops | Shows the current activity within InnoDB, including the number of queries in progress and queries queued to execute. Queued queries indicates a greater number of requests than InnoDB thread concurrency can handle. |
| MySQL InnoDB Current Locks | mysql-innodb-current-locks | Number of row locks currently held and the number of row locks currently being waited for. |
| MySQL InnoDB Deadlocks | mysql-innodb-deadlocks | Number of deadlocks detected by InnoDB. |
| MySQL InnoDB Doublewrite Buffer | mysql-innodb-doublewrite-buffer | Number of pages that have been written to the doublewrite buffer and the number of doublewrite operations performed. |
| MySQL InnoDB File I/O | mysql-innodb-file-io | Pending IO operations within InnoDB. A large number of pending operations usually indicates an IO bottleneck. |
| MySQL InnoDB Fsync Ops | mysql-innodb-fsync-ops | Number of fsync operations to sync data to disk. High pending fsyncs usually indicates an IO bottleneck. |
| MySQL InnoDB History List Length | mysql-innodb-history-list-length | Number of unflushed changes in update undo logs for committed transactions. |
| MySQL InnoDB I/O Ops | mysql-innodb-io-ops | Number of OS file reads and writes done by InnoDB. |
| MySQL InnoDB Mutex Locks | mysql-innodb-lock-operations | Number of OS lock waits. |
| MySQL InnoDB Log I/O Ops | mysql-innodb-log-io-ops | Write activity to the InnoDB Log File. High pending writes/fsyncs usually indicates an IO bottleneck. |
| MySQL InnoDB Log Pending | mysql-innodb-log-pend | Number of pending checkpoint writes and pending writes to the InnoDB redo logs. |
| MySQL InnoDB Log Sequence | mysql-innodb-log-seq | Last checkpoint and current log sequence. |
| MySQL InnoDB Log Writes | mysql-innodb-log-writes | Requested writes, and physical writes, to the redo log. log_waits is the number of times that the log buffer was too small and a wait was required for it to be flushed before continuing. |
| MySQL InnoDB LRU | mysql-innodb-lru | Buffer pool statistics about the number of pages moved (or not moved) to the head of the sublist of “new” pages. |
| MySQL InnoDB Master Thread | mysql-innodb-master-thread | The master thread in InnoDB is a thread that performs various tasks in the background. Most of these tasks are I/O related, such as flushing dirty pages from the buffer pool or writing changes from the insert buffer to the appropriate secondary indexes. |
| MySQL InnoDB Memory | mysql-innodb-memory | Memory used by the InnoDB dictionary and adaptive hash. |
| MySQL InnoDB Mutexes | mysql-innodb-mutexes | Number of times a mutex was unavailable and the number of threads that went to sleep while waiting (os_waits). |
| MySQL InnoDB Page Ops | mysql-innodb-page-ops | Pages created, read, and written in the InnoDB buffer pool by operations on InnoDB tables. |
| MySQL InnoDB Row Locks | mysql-innodb-row-locks | InnoDB row lock information, including average and total wait time, the number of row locks being waited for, and the number of total operations which waited for a lock. |
| MySQL InnoDB Row Ops | mysql-innodb-row-ops | Number of rows read, inserted, updated, or deleted from InnoDB tables. |
| MySQL InnoDB Transaction Locks | mysql-innodb-trx-locks | Number of transactions waiting on a lock. |
| MySQL InnoDB Transaction States | mysql-innodb-trx-states | Number of transactions in each state. |
| MySQL InnoDB Transaction Times | mysql-innodb-trx-times | Total time of transactions in each state. lock.time_us is the time spent waiting for a lock, for the transaction waiting the longest. |
| MySQL Query Latency Bands | mysql-latency-bands | Count of query executions within different latency bands. An increase in executions jumping to higher bands may indicate a stall in the server. |
| MySQL Processlist Commands Count | mysql-processlist-commands-count | Number of threads performing each command, from the MySQL PROCESSLIST. |
| MySQL Processlist Commands Time | mysql-processlist-commands-time | Total time that threads have spent performing each command, from the MySQL PROCESSLIST. |
| MySQL Processlist States Count | mysql-processlist-state-count | Number of threads in each state, from the MySQL PROCESSLIST. Most states correspond to very quick operations. If a thread stays in a given state for many seconds, there might be a problem that needs to be investigated. |
| MySQL Processlist States Time | mysql-processlist-state-time | Total time that threads have spent in each state, from the MySQL PROCESSLIST. Most states correspond to very quick operations. If a thread stays in a given state for many seconds, there might be a problem that needs to be investigated. |
| MySQL Query Latency | mysql-query-latency | Shows the average time for a given query to complete; spikes may indicate a general slowdown or they may indicate more extreme slowdowns in a few areas of your server workload. Consult your Query Latency Bands to determine which is the case. |
| MySQL Activity | mysql-status-activity | Summary of current MySQL activity, including number of executing queries and open connections. |
| MySQL Binlog Cache | mysql-status-binlog-cache | Number of transactions and nontransactions (“stmt”) that used the binary log cache. “disk_use” indicates the statements used the cache but exceeded the value of binlog_stmt_cache_size and so used a temporary file to store the statements. |
| MySQL Binlog Ops | mysql-status-binlog-ops | Number of commits and group commits to the binlog. |
| MySQL Commands | mysql-status-commands | Number of times each statement type has been executed. Metrics beginning with “comstmt” are for prepared statements. |
| MySQL Connections Per Second | mysql-status-connections-errors | Total number of connection attempts and connection errors, as well as the number of connections closed because the client did not close the connection. |
| MySQL Connections Pool | mysql-status-connections | The number of current connections and the maximum number of simultaneously used connections since the server started. |
| MySQL File Handles | mysql-status-file-handles | Number of tables and files that InnoDB has open. |
| MySQL File Opens | mysql-status-file-opens | Number of files and tables opened. If opened_tables is big, your table_open_cache value may be too small. |
| MySQL Handler Reads | mysql-status-handler-reads | Data about how MySQL is reading data from tables. Large numbers of handler_read_rnd and handler_read_rnd_next indicates your tables are poorly indexed or queries are not written to use the indexes you have. |
| MySQL Handler Row Ops | mysql-status-handler-row-ops | Number of requests to update, delete, or insert a row in a table. |
| MySQL MyISAM Key Cache Ops | mysql-status-myisam-key-cache-ops | Read and write requests from the key cache. |
| MySQL MyISAM Key Cache | mysql-status-myisam-key-cache | Size metrics for the MyISAM key cache. key_block_used represents the “high water mark” for usage. |
| MySQL Network Traffic | mysql-status-network-traffic | Bytes sent and received by the server to and from all connected clients. |
| MySQL Performance Schema Lost | mysql-status-performance-schema-lost | These variables provide information about instrumentation that could not be loaded or created due to memory constraints. If you are monitoring using the performance_schema (“off-host”) and “performance_schema_digest_lost” is not 0, some queries are not being tracked. Increase the value of performance_schema_digests_size. |
| MySQL Prepared Statements | mysql-status-prepared-statements | These metrics are for prepared statement commands, such as those executing and deallocating a statement. Their names refer to the COM_xxx command set used in the network layer. |
| MySQL Queries | mysql-status-queries | Rate of questions (only client requests) and queries (all executed statements), as well as executions slower than the long_query_time. |
| MySQL Query Cache Memory | mysql-status-query-cache-memory | Free and total memory available in the query cache. |
| MySQL Query Cache Ops | mysql-status-query-cache-ops | Operations on the query cache describing how it is currently being used. |
| MySQL Query Cache Usage | mysql-status-query-cache-usage | The number of queries registered in the query cache. |
| MySQL Questions per Connection | mysql-status-questions-per-connection | The number of statements executed by the server, per connection. This includes only statements sent to the server by clients and not statements executed within stored programs, unlike the Queries variable. This variable does not count COM_PING, COM_STATISTICS, COM_STMT_PREPARE, COM_STMT_CLOSE, or COM_STMT_RESET commands. |
| MySQL Replication Delay | mysql-status-replication-delay | The delay between the master and the slave, in microseconds. |
| MySQL Replication | mysql-status-replication | Replication metrics. If the value of open_temp_tables is greater than zero, it is not safe to shut down the slave. |
| MySQL Select Types | mysql-status-select-types | How MySQL performed SELECTs. If “select_full_join” and “select_range_check” are not 0, you should carefully check the indexes of your tables. “select_range” is normally not a critical issue even if the value is quite large. |
| MySQL Sorts | mysql-status-sorts | Indicates the number of times a query executed using each sort type. If “sort_merge_passes” is large, you should consider increasing the value of the sort_buffer_size system variable. |
| MySQL SSL Events | mysql-status-ssl-events | Number of SSL activities per second. If monitoring using the on-host method, queries sent over SSL-secured connections are not tracked by DPM. |
| MySQL Table Cache | mysql-status-table-cache | Hits and misses of table cache lookups. Overflows is the number of times, after a table is opened or closed, a cache instance has an unused entry and the size of the instance is larger than table_open_cache / table_open_cache_instances. |
| MySQL Table Locks | mysql-status-table-locks | The number of times that a request for a table lock could be granted immediately vs. after a wait. If “waited” is high and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication. |
| MySQL Temp usage | mysql-status-temp-usage | Metrics about MySQL’s use of temporary files and tables. If created_tmp_disk_tables is large, you may want to increase the tmp_table_size or max_heap_table_size value to lessen the likelihood that internal temporary tables in memory will be converted to on-disk tables. You can compare the number of internal on-disk temporary tables created to the total number of internal temporary tables created by comparing the values of the created_tmp_disk_tables and created_tmp_tables variables. |
| MySQL Threads | mysql-status-threads | Thread information from SHOW STATUS. If “threads_created” is large, you may want to increase the thread_cache_size value. |
PostgreSQL Charts
| Chart Title | Chart ID | Chart Description |
|---|---|---|
| PgBouncer Client Connections Usage | pgbouncer-cl-conn-pct | Number of client connections that are either active (can process queries) or waiting (connections waiting for the server) as a percentage of the configured maximum (max_client_conn). |
| PgBouncer Client Connections | pgbouncer-cl-conn | Client connections that are linked to server connection and can process queries (active) and client connections have sent queries but have not yet got a server connection (waiting). |
| PgBouncer Max Wait | pgbouncer-maxwait | How long the first (oldest) client in queue has waited, in microseconds. If this starts increasing, then the current pool of servers does not handle requests quick enough. Reason may be either overloaded server or just too small of a pool_size setting. |
| PgBouncer Query Latency | pgbouncer-query-latency | Shows the average time for a given query to complete; spikes may indicate a general slowdown or they may indicate more extreme slowdowns in a few areas of your server workload. Consult your Query Latency Bands to determine which is the case. |
| PgBouncer Requests | pgbouncer-requests | Total number of SQL requests pooled by pgbouncer. |
| PgBouncer Server Connections | pgbouncer-sv-conn | Connection pool statistics. Idle connections can be used immediately; used connections need server_check_delay to be run on it before it can be used. |
| PgBouncer Network Traffic | pgbouncer-traffic | Total volume, in bytes, of network traffic sent and received by PgBouncer. |
| PostgreSQL Cache Hit Ratio | pgsql-cache-hit-ratio | The percentage of blocks served by the cache. |
| PostgreSQL Cache Miss Ratio | pgsql-cache-miss-ratio | The percentage of blocks read not served by the cache. |
| PostgreSQL Totals | pgsql-host-totals-queries | Total query time (in microseconds) with total queries executed and average latency. |
| PostgreSQL Query Latency Bands | pgsql-latency-bands | Shows a count of query executions within different latency bands. An increase in executions jumping to higher bands may indicate a stall in the server. |
| PostgreSQL Query Latency | pgsql-query-latency | Shows the average time for a given query to complete; spikes may indicate a general slowdown or they may indicate more extreme slowdowns in a few areas of your server workload. Consult your Query Latency Bands to determine which is the case. |
| PostgreSQL Replication Delay | pgsql-repl-delay | The delay between this standby and the primary, in microseconds. |
| PostgreSQL Replicas Count | pgsql-repl-secondaries | The number of secondaries this instance is replicating its data to. |
| PostgreSQL Backends | pgsql-status-backends | Shows the total number of backends (forked processes) and the number of backends in each state, such as active, idle, etc. |
| PostgreSQL Database Blocks | pgsql-status-blocks | Number of blocks read from disk (blks_read) and from the cache without having to go to disk (blks_hit). |
| PostgreSQL BGWriter Buffers | pgsql-status-buffers | Shows the total number of buffers allocated, written directly by a backend and written during checkpoint operations. If you see an increasing number of buffers being written directly by backends, this indicates that you have a write-heavy load that is generating dirty buffers so quickly that it can’t keep up with the rate of checkpoints. It’s generally better for performance if the majority of buffers are written to disk during checkpoints, as opposed to directly by backends or by the background writer. |
| PostgreSQL Checkpoint Times | pgsql-status-checkpoints-time | The amount of time spent in checkpoint processing where files are either synchronized or written to disk. |
| PostgreSQL Checkpoints | pgsql-status-checkpoints | Number of requested checkpoints (checkpoints_req) and scheduled checkpoints (checkpoints_timed) that have been performed. |
| PostgreSQL Locks | pgsql-status-locks-counts | Total number of locks being waited for (awaited.count) or held (held.count) of a particular type. |
| PostgreSQL Lock Wait Times | pgsql-status-locks-durations | Total time spent waiting for (awaited.wait_us) or holding (held.wait_us) a lock of a particular type. |
| PostgreSQL Longest Running Vacuum | pgsql-status-longest-vacuum | The longest running duration of a vacuum command either manual or automatic. |
| PostgreSQL Transactions | pgsql-status-transactions | Shows the total number of transactions that were committed or rolled back. |
| PostgreSQL Tuples | pgsql-status-tuples | Shows the total number of tuples (rows) that were affected by the different operations, such as total number retrieved or inserted. |
| PostgreSQL Temporary Data Created | pgsql-temp-data | Amount of temporary data written by PostgreSQL, in bytes. |
Agent OS Metrics
These are metrics from the host where the DPM agent is installed. When monitoring RDS or Aurora, refer to the CloudWatch charts for metrics like CPU and disk utilization.
| Chart Title | Chart ID | Chart Description |
|---|---|---|
| CPU Utilization | machine-cpu-utilization | The percent of time the CPU(s) were busy. |
| Disk Available | machine-disk-available | The percent of disk space that is available. |
| Disk Utilization | machine-disk-utilization | The percent of time the disks were busy. |
| Memory Utilization | machine-memory-utilization | The percent of memory being used. |
| OS Context Switches | os-context-switches | The number of context switches the system underwent. Context switching is generally computationally intensive. |
| OS CPU Credit Balance | os-cpu-ec2-balance | The number of earned CPU credits that an instance has accrued since it was launched or started. For T2 Standard, the CPUCreditBalance also includes the number of launch credits that have been accrued. The credit balance has a maximum limit, determined by the instance size. Once the limit is reached, any new credits that are earned are discarded. |
| OS CPU Credit Usage | os-cpu-ec2-usage | The number of CPU credits spent by the instance for CPU utilization. One CPU credit equals one vCPU running at 100% utilization for one minute or an equivalent combination of vCPUs, utilization, and time. |
| OS CPU Usage | os-cpu-utilization | Number of microseconds the CPU spent in each state. |
| OS Average Disk Latency | os-disk-io-latency | The average amount of time taken for the disk to respond to a read or write request. |
| OS Disk I/O Ops | os-disk-io-ops | The number of read and write operations per second. |
| OS Disk I/O Sectors | os-disk-io-sectors | The number of disk sectors read from, or written to, per second. |
| OS Disk Space | os-disk-space | Amount of free and used disk space, in bytes. |
| OS Network Packets | os-network-packets | Number of packets sent to and from the server. |
| OS Network Bytes | os-network-traffic | Number of bytes sent to and from the server. |
| OS Per disk space | os-per-disk-space | Free and used disk space, by volume name. |
| OS Processes | os-processes | Number of processes currently running, and the number of processes blocked, waiting for IO. |
CloudWatch Charts
| Chart Title | Chart ID | Chart Description |
|---|---|---|
| MySQL CloudWatch Bin Log Disk Usage | mysql-cw-bin-log-disk-usage | The amount of disk space occupied by binary logs on the master. Applies to MySQL read replicas. |
| MySQL CloudWatch CPU Credit Balance | mysql-cw-cpu-credit-balance | The number of earned CPU credits that an instance has accrued since it was launched or started. For T2 Standard, the CPUCreditBalance also includes the number of launch credits that have been accrued. The credit balance has a maximum limit, determined by the instance size. Once the limit is reached, any new credits that are earned are discarded. |
| MySQL CloudWatch CPU Credit Usage | mysql-cw-cpu-credit-usage | The number of CPU credits spent by the instance for CPU utilization. One CPU credit equals one vCPU running at 100% utilization for one minute or an equivalent combination of vCPUs, utilization, and time. |
| MySQL CloudWatch CPU Utilization | mysql-cw-cpu-utilization | The percentage of CPU utilization. |
| MySQL CloudWatch Database Connections | mysql-cw-database-connections | The number of database connections in use. |
| MySQL CloudWatch Disk Queue Depth | mysql-cw-disk-queue-depth | The number of outstanding IOs (read/write requests) waiting to access the disk. |
| MySQL CloudWatch Free Storage Space | mysql-cw-free-storage-space | The amount of available storage space. |
| MySQL CloudWatch Freeable Memory | mysql-cw-freeable-memory | The amount of available random access memory. |
| MySQL CloudWatch Network Receive Throughput | mysql-cw-network-receive-throughput | The incoming (Receive) network traffic on the DB instance, including both customer database traffic and Amazon RDS traffic used for monitoring and replication. |
| MySQL CloudWatch Network Transmit Throughput | mysql-cw-network-transmit-throughput | The outgoing (Transmit) network traffic on the DB instance, including both customer database traffic and Amazon RDS traffic used for monitoring and replication. |
| MySQL CloudWatch Read IOPS | mysql-cw-read-iops | The average number of disk read I/O operations per second. |
| MySQL CloudWatch Read Latency | mysql-cw-read-latency | The average amount of time taken per disk I/O operation. |
| MySQL CloudWatch Read Throughput | mysql-cw-read-throughput | The average number of bytes read from disk per second. |
| MySQL CloudWatch Swap Usage | mysql-cw-swap-usage | The amount of swap space used on the DB instance. |
| MySQL CloudWatch Write IOPS | mysql-cw-write-iops | The average number of disk write I/O operations per second. |
| MySQL CloudWatch Write Latency | mysql-cw-write-latency | The average amount of time taken per disk I/O operation. |
| MySQL CloudWatch Write Throughput | mysql-cw-write-throughput | The average number of bytes written to disk per second. |
| PostgreSQL CloudWatch CPU Credit Balance | pgsql-cw-cpu-credit-balance | The number of earned CPU credits that an instance has accrued since it was launched or started. For T2 Standard, the CPUCreditBalance also includes the number of launch credits that have been accrued. The credit balance has a maximum limit, determined by the instance size. Once the limit is reached, any new credits that are earned are discarded. |
| PostgreSQL CloudWatch CPU Credit Usage | pgsql-cw-cpu-credit-usage | The number of CPU credits spent by the instance for CPU utilization. One CPU credit equals one vCPU running at 100% utilization for one minute or an equivalent combination of vCPUs, utilization, and time. |
| PostgreSQL CloudWatch CPU Utilization | pgsql-cw-cpu-utilization | The percentage of CPU utilization. |
| PostgreSQL CloudWatch Database Connections | pgsql-cw-database-connections | The number of database connections in use. |
| PostgreSQL CloudWatch Disk Queue Depth | pgsql-cw-disk-queue-depth | The number of outstanding IOs (read/write requests) waiting to access the disk. |
| PostgreSQL CloudWatch Free Storage Space | pgsql-cw-free-storage-space | The amount of available storage space. |
| PostgreSQL CloudWatch Freeable Memory | pgsql-cw-freeable-memory | The amount of available random access memory. |
| PostgreSQL CloudWatch Network Receive Throughput | pgsql-cw-network-receive-throughput | The incoming (Receive) network traffic on the DB instance, including both customer database traffic and Amazon RDS traffic used for monitoring and replication. |
| PostgreSQL CloudWatch Network Transmit Throughput | pgsql-cw-network-transmit-throughput | The outgoing (Transmit) network traffic on the DB instance, including both customer database traffic and Amazon RDS traffic used for monitoring and replication. |
| PostgreSQL CloudWatch Oldest Replication Slot Lag | pgsql-cw-oldest-replication-slot-lag | The lagging size of the replica lagging the most in terms of WAL data received. |
| PostgreSQL CloudWatch Read IOPS | pgsql-cw-read-iops | The average number of disk read I/O operations per second. |
| PostgreSQL CloudWatch Read Latency | pgsql-cw-read-latency | The average amount of time taken per disk I/O operation. |
| PostgreSQL CloudWatch Read Throughput | pgsql-cw-read-throughput | The average number of bytes read from disk per second. |
| PostgreSQL CloudWatch Swap Usage | pgsql-cw-swap-usage | The amount of swap space used on the DB instance. |
| PostgreSQL CloudWatch Transaction Logs Disk Usage | pgsql-cw-transaction-logs-disk-usage | The disk space used by transaction logs. |
| PostgreSQL CloudWatch Transaction Logs Generation | pgsql-cw-transaction-logs-generation | The size of transaction logs generated per second. |
| PostgreSQL CloudWatch Write IOPS | pgsql-cw-write-iops | The average number of disk write I/O operations per second. |
| PostgreSQL CloudWatch Write Latency | pgsql-cw-write-latency | The average amount of time taken per disk I/O operation. |
| PostgreSQL CloudWatch Write Throughput | pgsql-cw-write-throughput | The average number of bytes written to disk per second. |
| RDS CPU | rds-os-cpu | The percent of time the CPU(s) spent per state. |
| RDS Load Average | rds-os-loadavg | Number of processes requesting CPU time over the last N minutes. |
| RDS Memory Usage | rds-os-mem | Current memory usage information, in bytes. |
| RDS Network Traffic | rds-os-net | Number of bytes received (rx) and sent (tx) from the database per second. |
| RDS Storage IOPS | rds-os-storage-iops | Disk read/write IOPS and TPS. |
| RDS Storage Latency | rds-os-storage-latency | The average amount of time taken for the disk to respond to a read or write request. |
| RDS Storage Throughput | rds-os-storage-tput | The number of read and write operations performed per second. |
| RDS Storage Usage | rds-os-storage-usage | Used and free disk space. |
| RDS Swap Usage | rds-os-swap | Swap space usage, in bytes, including the total, free, and memory swapped in/from disk. |
| RDS Tasks | rds-os-tasks | The number of OS processes in each state. |