The AWS RDS v2 sensor monitors the performance of a Amazon Web Services (AWS) Relational Database Service (RDS) database by reading its data from Amazon CloudWatch via the AWS API.
If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?
This setting is for your information only. You cannot change it.
Tags
Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.
It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).
For performance reasons, it can take some minutes until you can filter for new tags that you added.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
aws
cloudwatch
rds
cloudwatchsensor
Priority
Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority () to the highest priority ().
AWS RDS Specific
AWS RDS Specific
Setting
Description
Database Identifier
The database identifier of the AWS RDS database that this sensor monitors.
Engine
The engine family name of the AWS RDS database that this sensor monitors.
Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.
You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.
Graph Type
Define how different channels are shown for this sensor:
Show channels independently (default): Show a graph for each channel.
Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic. You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).
Stack Unit
This setting is only visible if you select Stack channels on top of each other above.
Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.
Debug Options
Debug Options
Setting
Description
Result Handling
Define what PRTG does with the sensor result:
Discard result: Do not store the sensor result.
Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file name is Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites this file with each scanning interval.
This option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.
In a cluster, PRTG stores the result in the PRTG data directory of the master node.
Inherited Settings
By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.
This sensor has a fixed minimum scanning interval for performance reasons. You cannot use a shorter scanning interval. Consequently, shorter scanning intervals in the Monitoring settings are not available for this sensor.
The minimum scanning interval of this sensor is 5 minutes.
The recommended scanning interval of this sensor is 5 minutes.
Scanning Interval
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.
Schedules, Dependencies, and Maintenance Window
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
Access Rights
Access Rights
For more information, see section Root Group Settings, section Access Rights.
Channel Unit Configuration
Which channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.
Channel Unit Configuration
For more information, see section Root Group Settings, section Channel Unit Configuration.
Supported Metrics
The AWS RDS v2 sensor supports the following metrics:
BinLogDiskUsage (MB)
CPUUtilization (Average)
CPUCreditUsage (Average)
CPUCreditBalance (Average)
DatabaseConnections (Count)
DiskQueueDepth (Count)
FreeableMemory (MB)
FreeStorageSpace (MB)
NetworkReceiveThroughput (Byte/Second)
NetworkTransmitThroughput (Byte/Second)
ReadIOPS (Count/Second)
ReadLatency (Milliseconds)
ReadThroughput (Byte/Second)
ReplicaLag (Milliseconds)
SwapUsage (MB)
WriteIOPS (Count/Second)
WriteLatency (Milliseconds)
WriteThroughput (Byte/Second)
Supported Dimensions
The AWS RDS v2 sensor supports the following dimensions:
DBInstanceIdentifier
Channel List
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel
Description
Bin Log Disk Usage
The bin log disk usage
CPU Credit Balance
The CPU credit balance
CPU Credit Usage
The CPU credit usage
CPU Utilization
The CPU usage
This channel is the primary channel by default.
Database Connections
The percentage of database connections in use
Disk Queue Depth
The number of outstanding read and write requests waiting to access the disk
Downtime
In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status
Free Storage Space
The amount of available storage space
Freeable Memory
The freeable memory
Network Receive Throughput
The incoming (receive) network traffic
Network Transmit Throughput
The outgoing (transmit) network traffic
Read IOPS
The average number of disk read IOPS
Read Latency
The read latency
Read Throughput
The average number of bytes read from disk
Replica Lag
The amount of time a read replica DB instance lags behind the source DB instance
Swap Usage
The swap usage
Write IOPS
The average number of disk write IOPS
Write Latency
The average amount of time taken per disk read and write operation
Write Throughput
The number of disk write operations
More
KNOWLEDGE BASE
How do I set permissions for the Amazon Web Services (AWS) API key to use certain sensors in PRTG?