<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: AWS RDS v2 Sensor
The AWS RDS v2 sensor monitors the performance of a Relational Database Service (RDS) database by reading its data from Amazon CloudWatch via the AWS API.
If you use the same Identity and Access Management (IAM) policy that you use for the Amazon CloudWatch RDS sensor, you must update it. For more information, see the Knowledge Base: How do I set permissions for the Amazon Web Services (AWS) API key to use certain sensors in PRTG?
This sensor is in beta status. The operating methods and the available settings can change at any time. Do not expect that all functions work properly, or that this sensor works as expected at all. Be aware that this sensor can be removed from PRTG at any time.
AWS RDS v2 Sensor
For a list of metrics that this sensor supports, see section Supported Metrics.
For a list of dimensions that this sensor supports, see section Supported Dimensions.
For a list of regions that this sensor supports, see section List of Supported AWS Regions and Their Codes.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
Sensor in Other Languages
- Dutch: AWS RDS v2
- French: AWS RDS v2
- German: AWS RDS v2
- Japanese: AWS RDS v2
- Portuguese: AWS RDS v2
- Russian: AWS RDS v2
- Simplified Chinese: AWS RDS v2
- Spanish: AWS RDS v2
Remarks
Detailed Requirements
Add Sensor
The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the settings that are required to create the sensor. You can change nearly all settings on the sensor's Settings tab after creation.
PRTG looks for available databases.
This can take up to several minutes.
The settings that you select in the Add Sensor dialog are valid for all sensors that you create when you finish the dialog.
AWS RDS Specific
|
|
Name
|
Select the load balancers that you want to monitor. PRTG creates one sensor for each name that you select.
Enable check boxes in front of the respective lines to select the items. Use the check box in the table header to select all items or to cancel the selection. In large tables, use the search function in the upper-right corner.
|
Basic Sensor Settings
Click the Settings tab of a sensor to change its settings.
Basic Sensor Settings
|
|
Sensor Name
|
Enter a name to identify the sensor.
|
Parent Tags
|
Shows tags that the sensor inherits from its parent device, parent group, and parent probe.
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 ().
|
Usually, a sensor connects to the IP Address/DNS Name of the parent device. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings.
AWS RDS Specific
AWS RDS Specific
|
|
Database Identifier
|
Shows the database identifier of the Amazon RDS database that this sensor monitors.
PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.
|
Engine
|
Shows the engine family name of the Amazon RDS database that this sensor monitors.
PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.
|
Region
|
Shows the region in which the Amazon RDS instance runs.
PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.
For a list of regions that this sensor supports, see section List of Supported AWS Regions and Their Codes.
|
Sensor Display
Sensor Display
|
|
Primary Channel
|
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 enable Stack channels on top of each other as Graph Type. 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
|
|
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.
For more information, see section Inheritance of Settings.
Scanning Interval
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:
- 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:
Channel List
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
|
|
Bin Log Disk Usage
|
The bin log disk usage in bytes
|
CPU Credit Balance
|
The CPU credit balance
|
CPU Credit Usage
|
The CPU credit usage
|
CPU Utilization
|
The CPU usage in percent
This channel is the primary channel by default.
|
Database Connections
|
The number of database connections in use in percent
|
Disk Queue Depth
|
The number of outstanding I/Os (read/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 in percent.
|
Free Storage Space
|
The amount of available storage space in bytes
|
Freeable Memory
|
The freeable memory in bytes
|
Network Receive Throughput
|
The incoming (receive) network traffic in bytes per second
|
Network Transmit Throughput
|
The outgoing (transmit) network traffic in bytes per second
|
Read IOPS
|
The average number of disk read I/O operations per second
|
Read Latency
|
The read latency in milliseconds (msec)
|
Read Throughput
|
The average number of bytes read from disk per second
|
Replica Lag
|
The amount of time a read replica DB instance lags behind the source DB instance in seconds
|
Swap Usage
|
The swap usage in bytes
|
Write IOPS
|
The average number of disk write I/O operations per second
|
Write Latency
|
The average amount of time taken per disk I/O operation in msec
|
Write Throughput
|
The number of disk write operations per second
|
More
Knowledge Base
What are beta sensors and how can I use them?
How do I set permissions for the Amazon Web Services (AWS) API key to use certain sensors in PRTG?
What security features does PRTG include?