This topic contains information about the features released in PATROL for Amazon Web Services 3.0.00.
Monitor multiple AWS accounts by using trusted account
Monitor multiple Amazon Web Services (AWS) accounts by using a single account as the trusted or main account. The trusted account is responsible for retrieving data from other accounts. For more information, see Prerequisites for configuring AWS instance.
Option to configure device mapping
Enable or disable device mapping for a monitoring configuration. You can create the device name based on any of the following options:
- Private DNS (Private IPv4 address)
- Public DNS (Public IPv4 address)
- Instance ID
- Name Tag
For more information, see Configuring the Amazon Web Services monitor type.
New services added for monitoring
Monitor the following AWS services:
- Elastic Kubernetes Service
- Virtual Private Cloud
In addition, monitoring capabilities are enhanced for the following services:
- Relational Database Service: Added support to monitor Aurora DB
- ElastiCache: Added support to monitor Redis Engine
The following table lists the application classes that are added:
|Elastic Kubernetes Service|
|Virtual Private Cloud|
|Relational Database Clusters under the Relational Database Service||Relational Database Service Cluster (AWS_RDS_CLUSTER)|
|Redis Engine under ElastiCache|
Filter service instances by tags
Use tag names to filter service instances that you want to monitor. For more information, see Configuring the Amazon Web Services monitor type.
Optional to provide proxy server credentials
If you do not want to authenticate proxy server configuration, you can choose to skip entering the username and password in the Proxy Server Configuration section. For more information, see Configuring the Amazon Web Services monitor type.
Additional metrics added to Relational Database Service monitoring
The following attributes are added to monitor Relational Database Service. For more information, see Relational Database Service (AWS_RDS).
|Active Transactions (ActiveTransactions)||DDL Latency (DDLLatency)||Network Receive Throughput (NetworkReceiveThroughput)|
|Aurora Bin log Replica Lag (AuroraBinlogReplicaLag)||DDL Throughput (DDLThroughput)||Network Throughput (NetworkThroughput)|
|Aurora Replica Lag (AuroraReplicaLag)||Delete Latency (DeleteLatency)||Network Transmit Throughput (NetworkTransmitThroughput)|
|Aurora Replica Lag Maximum (AuroraReplicaLagMaximum)||Delete Throughput (DeleteThroughput)||Number of Binary Log Files (NumBinaryLogFiles)|
|Aurora Replica Lag Minimum (AuroraReplicaLagMinimum)||DML Latency (DMLLatency)||Queries (Queries)|
|Blocked Transactions (BlockedTransactions)||DML Throughput (DMLThroughput)||Result Set Cache Hit Ratio (ResultSetCacheHitRatio)|
|Buffer Cache Hit Ratio (BufferCacheHitRatio)||Engine Uptime (EngineUptime)||Row Lock Time (RowLockTime)|
|Commit Latency (CommitLatency)||Free Local Storage (FreeLocalStorage)||Select Latency (SelectLatency)|
|Commit Throughput (CommitThroughput)||Insert Throughput (InsertThroughput)||Select Throughput (SelectThroughput)|
|CPU Credit Balance (CPUCreditBalance)||Login Failures (LoginFailures)||Update Latency (UpdateLatency)|
|CPU Credit Usage (CPUCreditUsage)||Maximum Used Transaction IDs (MaximumUsedTransactionIDs)||Update Throughput (UpdateThroughput)|
Ability to add multiple dimensions to custom metrics
Add multiple dimensions to the custom metric configurations. For more information, see Configuring the Amazon Web Services monitor type.