The AWS ELB v2 sensor monitors the performance of an Amazon Web Services (AWS) Elastic Load Balancing (ELB) load balancer by reading its data from Amazon CloudWatch via the AWS API.
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 load balancers.
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 ELB Specific
Setting
Description
Name
Select the load balancers that you want to monitor. PRTG creates one sensor for each load balancer 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.
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
elb
cloudwatchelb
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 ELB Specific
AWS ELB Specific
Setting
Description
ID
Shows the ID of the AWS ELB load balancer that this sensor monitors.
PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.
Name
Shows the name of the AWS ELB load balancer that this sensor monitors.
PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.
Type
Shows the type of the AWS ELB load balancer 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 AWS ELB load balancer runs.
PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.
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
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 1 minute.
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 ELB v2 sensor supports the following metrics:
ActiveConnectionCount (Sum)
ActiveFlowCount (Average)
ConsumedLCUs (Sum)
HealthyHostCount (Minimum)
HTTPCode_ELB_4XX_Count (Sum)
HTTPCode_ELB_5XX_Count (Sum)
HTTPCode_Target_4XX_Count (Sum)
HTTPCode_Target_5XX_Count (Sum)
NewConnectionCount (Sum)
NewFlowCount (Sum)
PeakBytesPerSecond (Maximum)
RuleEvaluations (Sum)
TargetConnectionErrorCount (Sum)
TargetResponseTime (Average)
TCP_Client_Reset_Count (Sum)
TCP_ELB_Reset_Count (Sum)
TCP_Target_Reset_Count (Sum)
UnhealthyHostCount (Maximum)
Supported Dimensions
The AWS ELB v2 sensor supports the following dimensions:
Load Balancer
Channel List
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel
Description
Active Connection Count
The number of concurrent active Transmission Control Protocol (TCP) connections
Active Flow Count
The number of concurrent flows
Consumed LCU's
The number of load balancer capacity units (LCU) used by the load balancer
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
ELB 4XX Count
The number of HTTP 4XX client error codes
ELB 5XX Count
The number of HTTP 5XX server error codes
Healthy Host Count
The number of targets that are considered healthy
New Connection Count
The number of new TCP connections
New Flow Count
The number of new flows
Peak Bytes
Highest average throughput
Processed Bytes
The number of bytes processed
Rule Evaluations
The number of rules processed
Target 4XX Count
The number of HTTP response codes generated by the targets
Target 5XX Count
The number of HTTP response codes generated by the targets
Target Connection Error Count
The number of connections that were not successfully established
Target Response Time
The response time of the target
TCP Client Reset Count
The number of number of reset (RST) packets sent from a client to a target
TCP ELB Reset Count
The number of RST packets generated by the load balancer
TCP Target Reset Count
The number of RST packets sent from a target to a client
Unhealthy Host Count
The number of targets that are considered unhealthy
More
KNOWLEDGE BASE
How do I set permissions for the Amazon Web Services (AWS) API key to use certain sensors in PRTG?