PRTG Manual: AWS ELB v2 Sensor
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.
If you use the same Identity and Access Management (IAM) policy that you use for this 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 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
Consider the following remarks and requirements for this sensor:
Remark |
Description |
---|---|
Permissions for the AWS API key |
This sensor requires permissions for the AWS API key. 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? |
Credentials |
This sensor requires credentials for AWS. |
Load balancers |
This sensor supports Application Load Balancer and Network Load Balancer. |
Performance impact |
This sensor has a low performance impact. |
Pricing |
Amazon can charge 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). |
Add Sensor dialog |
It can take up to several minutes before objects appear in the Add Sensor dialog. |
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.
|
IPv6 |
This sensor supports IPv6. |
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
- aws
- cloudwatch
- cloudwatchsensor
- elb
For more information about basic sensor settings, see section Sensor Settings.
Setting |
Description |
---|---|
ID |
The ID of the AWS ELB load balancer that this sensor monitors. |
Name |
The name of the AWS ELB load balancer that this sensor monitors. |
Type |
The type of the AWS ELB load balancer that this sensor monitors. |
Region |
The region in which the AWS ELB load balancer runs. For a list of regions that this sensor supports, see section Supported AWS Regions and Their Codes. |
Setting |
Description |
---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, PRTG displays the last value of the primary channel 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 this sensor shows different channels:
|
Stack Unit |
This setting is only visible if you select Stack channels on top of each other above. Select a unit from the list. PRTG stacks all channels with this unit 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:
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. |
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.
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 target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Active Connection Count |
The number of concurrent active TCP connections |
Active Flow Count |
The number of concurrent flows |
Consumed LCUs |
The number of LCUs that the load balancer uses |
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 |
The 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 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 |
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?