<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> 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.

i_round_redIf 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?

AWS ELB v2 Sensor

AWS ELB v2 Sensor

i_square_cyanFor a list of metrics that this sensor supports, see section Supported Metrics.

i_square_cyanFor a list of dimensions that this sensor supports, see section Supported Dimensions.

i_square_cyanFor a list of regions that this sensor supports, see section List of Supported AWS Regions and Their Codes.

i_square_cyanFor a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Sensor in Other Languages

  • 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

Remarks

  • 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.

Detailed Requirements

Requirement

Description

Permissions for the AWS API key

This sensor requires sufficient rights to query data from the AWS API

i_square_cyanFor 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?

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 load balancers.

i_round_blueThis can take up to several minutes.

i_round_blueThe 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.

i_round_blueEnable 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

Basic Sensor 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.

i_round_blueThis 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.

i_round_blueIt is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

i_round_blueFor 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 (i_priority_1) to the highest priority (i_priority_5).

i_round_blueUsually, 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

AWS ELB Specific

Setting

Description

ID

Shows the ID of the AWS ELB load balancer that this sensor monitors.

i_round_bluePRTG 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.

i_round_bluePRTG 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.

i_round_bluePRTG 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.

i_round_bluePRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.

i_square_cyanFor a list of regions that this sensor supports, see section List of Supported AWS Regions and Their Codes.

Sensor Display

Sensor Display

Sensor Display

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.

i_round_blueYou can set a different primary channel later by clicking b_channel_primary 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.
    i_round_redYou 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

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.

i_podThis option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.

i_round_blueIn 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 b_inherited_enabled under the corresponding setting name to disable the inheritance and to display its options.

i_square_cyanFor more information, see section Inheritance of Settings.

Scanning Interval

i_round_blueThis 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.

i_round_blueThe minimum scanning interval of this sensor is 1 minute.

i_round_blueThe recommended scanning interval of this sensor is 5 minutes.

Scanning Interval

Scanning Interval

i_square_cyanFor more information, see section Root Group Settings, section Scanning Interval.

Schedules, Dependencies, and Maintenance Window

i_round_blueYou 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

Schedules, Dependencies, and Maintenance Window

i_square_cyanFor more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.

Access Rights

Access Rights

Access Rights

i_square_cyanFor more information, see section Root Group Settings, section Access Rights.

Channel Unit Configuration

i_round_blueWhich 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

Channel Unit Configuration

i_square_cyanFor 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

i_round_blueWhich channels the sensor actually shows might depend on the target 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

More

i_square_blueKNOWLEDGE 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?