PRTG Manual: AWS ELB v2 Sensor
The AWS ELB v2 sensor monitors the performance of an Elastic Load Balancing (ELB) load balancer 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 ELB 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?
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.
- Dutch: AWS ELB v2
- French: AWS ELB v2
- German: AWS ELB v2
- Japanese: AWS ELB v2
- Portuguese: AWS ELB v2
- Russian: AWS ELB v2
- Simplified Chinese: AWS ELB v2
- Spanish: AWS ELB v2
- This sensor requires credentials for AWS in settings that are higher in the object hierarchy, for example, in the settings of the parent device.
- This sensor requires permissions for the AWS API key.
- Amazon charges you based on the number of API calls that the sensor sends to the Amazon servers. For more information, see Amazon CloudWatch Pricing – Amazon Web Services (AWS).
- This sensor supports Application Load Balancer and Network Load Balancer.
- This sensor supports the IPv6 protocol.
- This sensor has a low performance impact.
Requirement |
Description |
---|---|
Credentials for AWS |
This sensor requires credentials for AWS in settings that are higher in the object hierarchy, for example, in the settings of the parent device. |
Permissions for the AWS API key |
This sensor requires sufficient rights to query data from 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.
|
Click the Settings tab of a sensor to change its settings.
Setting |
Description |
---|---|
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.
|
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.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
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 ( |
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.
Setting |
Description |
---|---|
ID |
Shows the ID of the AWS ELB load balancer that this sensor monitors.
|
Name |
Shows the name of the AWS ELB load balancer that this sensor monitors.
|
Type |
Shows the type of the AWS ELB load balancer that this sensor monitors.
|
Region |
Shows the region in which the AWS ELB load balancer runs.
|
Setting |
Description |
---|---|
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.
|
Graph Type |
Define how different channels are shown for this sensor:
|
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. |
Setting |
Description |
---|---|
Result Handling |
Define what PRTG does with the sensor result:
|
By default, all of the following 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.
Click to interrupt the inheritance.
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.
Setting |
Description |
---|---|
Scanning Interval |
Select a scanning interval from the dropdown list. The scanning interval determines the amount of time that the sensor waits between two scans. Choose from:
|
If a Sensor Query Fails |
Select the number of scanning intervals that the sensor has time to reach and to check a device again if a sensor query fails. Depending on the option that you select, the sensor can try to reach and to check a device again several times before the sensor shows the Down status. This can avoid false alarms if the monitored device only has temporary issues. For previous scanning intervals with failed requests, the sensor shows the Warning status. Choose from:
|
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.
Setting |
Description |
---|---|
Schedule |
Select a schedule from the list. You can use schedules to monitor during a certain time span (days or hours) every week. Choose from:
|
Maintenance Window |
Select if you want to set up a one-time maintenance window. During a maintenance window, monitoring stops for the selected object and all child objects. They show the Paused status instead. Choose between:
|
Maintenance Begins |
This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the start date and time of the one-time maintenance window. |
Maintenance Ends |
This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the end date and time of the one-time maintenance window. |
Dependency Type |
Select a dependency type. You can use dependencies to pause monitoring for an object depending on the status of a different object. You can choose from:
|
Dependency |
This setting is only visible if you enable Select a sensor above. Click |
Dependency Delay (Sec.) |
This setting is only visible if you select Select a sensor above. Define a time span in seconds for the dependency delay. After the master sensor for this dependency returns to the Up status, PRTG additionally delays the monitoring of the dependent objects by the time span you define. This can prevent false alarms, for example, after a server restart or to give systems more time for all services to start. Enter an integer value.
|
Click to interrupt the inheritance.
Setting |
Description |
---|---|
User Group Access |
Define the user groups that have access to the sensor. You see a table with user groups and group access rights. The table contains all user groups in your setup. For each user group, you can choose from the following group access rights:
|
Click to interrupt the inheritance.
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.
Setting |
Description |
---|---|
Channel Unit Types |
For each type of channel, select the unit in which PRTG displays the data. If you define this setting on probe, group, or device level, you can inherit these settings to all sensors underneath. You can set units for the following channel types (if available):
|
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)
The AWS ELB v2 sensor supports the following dimensions:
- Load Balancer
Which channels the sensor actually shows might depend on the monitored device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Active Connection Count |
The total number of concurrent active Transmission Control Protocol (TCP) connections |
Active Flow Count |
The total 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 in percent. |
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 total number of new TCP connections |
New Flow Count |
The total number of new flows |
Peak Bytes |
Highest average throughput |
Processed Bytes |
The total 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 total number of reset (RST) packets sent from a client to a target |
TCP ELB Reset Count |
The total RST packets generated by the load balancer |
TCP Target Reset Count |
The total RST packets sent from a target to a client |
Unhealthy Host Count |
The number of targets that are considered unhealthy |
Knowledge Base
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?
For more information about sensor settings, see the following sections: