AWS ELB¶

Use the "Cloud Sync" series of script packages in the script market to synchronize cloud monitoring and cloud asset data to TrueWatch

Configuration¶

Install Func¶

It is recommended to activate the TrueWatch integration - extensions - hosted version of Func: all prerequisites are automatically installed, please proceed with the script installation.

If you are deploying Func yourself, refer to Self-deploying Func

Install Script¶

Note: Please prepare the Amazon AK that meets the requirements in advance (for simplicity, you can directly grant global read-only permissions ReadOnlyAccess)

Activate Script in Hosted Version¶

1. Log in to the TrueWatch console
2. Click the 【Integration】 menu, select 【Cloud Account Management】
3. Click 【Add Cloud Account】, select 【AWS】, and fill in the required information on the interface. If you have already configured the cloud account information before, ignore this step.
4. Click 【Test】, after the test is successful, click 【Save】. If the test fails, please check if the relevant configuration information is correct and test again.
5. Click 【Cloud Account Management】, you can see the added cloud account in the list, click the corresponding cloud account to enter the details page.
6. Click the 【Integration】 button on the cloud account details page, find AWS ELB under the Not Installed list, click the 【Install】 button, and the installation interface will pop up for installation.

Manually Activate Script¶

1. Log in to the Func console, click 【Script Market】, enter the TrueWatch script market, search for integration_aws_elb, integration_aws_applicationelb, integration_aws_networkelb, integration_aws_gatewayelb

2. Click 【Install】, then enter the corresponding parameters: AWS AK ID, AK Secret, and account name.

3. Click 【Deploy Startup Script】, the system will automatically create the Startup script set and automatically configure the corresponding startup script.

4. After enabling, you can see the corresponding automatic trigger configuration in 「Management / Automatic Trigger Configuration」. Click 【Execute】 to execute immediately without waiting for the scheduled time. Wait a moment, you can view the execution task records and corresponding logs.

We have collected some configurations by default, see the Metrics section for details.

Verification¶

1. In 「Management / Automatic Trigger Configuration」, confirm whether the corresponding task has the corresponding automatic trigger configuration, and you can also check the corresponding task records and logs to check for any exceptions.
2. In TrueWatch, check whether the asset information exists in 「Infrastructure / Custom」.
3. In TrueWatch, check whether there is corresponding monitoring data in 「Metrics」.

Metrics¶

After configuring Amazon Cloud Monitoring, the default measurement sets are as follows. More metrics can be collected through configuration:

Amazon Cloud Monitoring Application Load Balancer Metrics Details

Amazon Cloud Monitoring Network Load Balancer Metrics Details

Amazon Cloud Monitoring Gateway Load Balancer Metrics Details

Amazon Cloud Monitoring Classic Load Balancer Metrics Details

Application Load Balancer Metrics¶

AWS/ApplicationELB namespace includes the following metrics for targets.

AWS/ApplicationELB namespace includes the following metrics for target group health. For more information, see Target Group Health.

AWS/ApplicationELB namespace includes the following metrics for Lambda functions registered as targets.

AWS/ApplicationELB namespace includes the following metrics for user authentication.

Network Load Balancer Metrics¶

Gateway Load Balancer Metrics¶

Classic Load Balancer Metrics¶

Load Balancer Metric Dimensions¶

To filter metrics for Application / Network / Gateway load balancers, use the following dimensions.

To filter metrics for Classic load balancers, use the following dimensions.

Object¶

The AWS ELB object data structure collected can be seen in 「Infrastructure - Custom」

{
  "measurement": "aws_aelb",
  "tags": {
    "name"                 : "app/openway/8e8d762xxxxxx",
    "RegionId"             : "cn-northwest-1",
    "LoadBalancerArn"      : "arn:aws-cn:elasticloadbalancing:cn-northwest-1:588271xxxxx:loadbalancer/app/openway/8e8d762xxxxxx",
    "State"                : "active",
    "Type"                 : "application",
    "VpcId"                : "vpc-2exxxxx",
    "Scheme"               : "internet-facing",
    "DNSName"              : "openway-203509xxxx.cn-northwest-1.elb.amazonaws.com.cn",
    "LoadBalancerName"     : "openway",
    "CanonicalHostedZoneId": "ZM7IZAIxxxxxx"
  },
  "fields": {
    "CreatedTime"         : "2022-03-09T06:13:31Z",
    "ListenerDescriptions": "{JSON data}",
    "AvailabilityZones"   : "{Availability Zone JSON data}",
    "message"             : "{Instance JSON data}"
  }
}

Note: The fields in tags, fields may change with subsequent updates

Tip 1: AWS ELB measurement sets are divided into four types based on different load balancers:

1. Application ELB corresponds to the measurement set aws_aelb
2. Network ELB corresponds to the measurement set aws_nelb
3. Gateway ELB corresponds to the measurement set aws_gelb
4. Classic ELB corresponds to the measurement set aws_elb

Tip 2: The value of tags.name is determined in two ways:

1. For Classic Load Balancers, the LoadBalancerName field is used.
2. For Application, Network, and Gateway Load Balancers, the end part of the load balancer ARN (LoadBalancerArn) is used.

For example, for a Network Load Balancer:

`LoadBalancerArn` is `arn:awS-cn:elasticloadbalancing:cn-northwest-1:xxxx1335135:loadbalancer/net/k8s-forethou-kodongin-xxxxa46f01/xxxxe75ae81d08c2`

The corresponding tags.name is net/k8s-forethou-kodongin-xxxxa46f01/xxxxe75ae81d08c2

Tip 3:

• fields.message, tags.AvailabilityZones are JSON serialized strings
• The tags.state field indicates the Load Balancers status, with possible values: active, provisioning, active_impaired, failed (the "classic" type load balancer instances do not have this field)
• The tags.Type field indicates the Load Balancers type, with possible values: application, network, gateway, classic
• The tags.Scheme field indicates the Load Balancers scheme, with possible values: internet-facing, internal
• The fields.ListenerDescriptions field is the list of listeners for this load balancer
• The fields.AvailabilityZones field indicates the Amazon Route 53 availability zone information associated with the load balancer