PRTG Manual: AWS ELB v2 Sensor

Permissions for the AWS API key

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

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?

Sensor Name

Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.

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?

Parent Tags

The 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
• 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 ().

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 List of Supported AWS Regions and Their Codes.

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 select Stack channels on top of each other above.

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.

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.

Active Connection Count

The number of concurrent active TCP connections

Active Flow Count

The number of concurrent flows

Consumed LCU's

The number of 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

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