AWS ELB¶

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

Configuration¶

Install Func¶

It is recommended to enable TrueWatch integration - extension - DataFlux Func (Automata): all prerequisites are automatically installed, please continue with script installation.

If you deploy Func yourself, refer to Self-deploy Func

Install Script¶

Note: Please prepare an Amazon Web Services AK that meets the requirements in advance (for simplicity, you can directly grant CloudWatch read-only access CloudWatchReadOnlyAccess)

To synchronize ECS cloud resource monitoring data, we install the corresponding collection script:

For AWS Application Load Balancer (AWS Application ELB), select "TrueWatch Integration (AWS-ApplicationELB Collection)" (ID: truewatch_aws_applicationelb)

For AWS Network Load Balancer (AWS Network ELB), select "TrueWatch Integration (AWS-NetworkELB Collection)" (ID: truewatch_aws_networkelb)

For AWS Gateway Load Balancer (AWS Gateway ELB), select "TrueWatch Integration (AWS-GatewayELB Collection)" (ID: truewatch_aws_gatewayelb)

For AWS Classic Load Balancer, select "TrueWatch Integration (AWS-ELB Collection)" (ID: truewatch_aws_elb)

After clicking [Install], enter the corresponding parameters: Amazon Web Services AK, Amazon Web Services account name.

Click [Deploy Startup Script], and the system will automatically create a Startup script set and automatically configure the corresponding startup script. In the startup script, ensure that 'regions' match the actual regions where the ELBs are located.

After enabling, you can see the corresponding automatic trigger configuration in "Manage / Automatic Trigger Configuration." Click [Execute] to immediately execute it once without waiting for the scheduled time. After a short wait, you can view the execution task records and corresponding logs.

If you want to collect the corresponding logs, you also need to enable the corresponding log collection script. If you want to collect bills, you need to enable the cloud bill collection script.

By default, we collect some configurations, for more details see the metrics section Configure Custom Cloud Object Metrics

Verification¶

1. In "Manage / Automatic Trigger Configuration," confirm whether the corresponding tasks have the corresponding automatic trigger configuration, and check the corresponding task records and logs for any abnormalities.
2. On the TrueWatch platform, under "Infrastructure / Custom," check if there is asset information.
3. On the TrueWatch platform, under "Metrics," check if there is corresponding monitoring data.

Metrics¶

After configuring Amazon Web Services - Cloud Monitoring, the default metric sets are as follows. You can collect more metrics through configuration:

Amazon Web Services Cloud Monitoring Application Load Balancer Metric Details

Amazon Web Services Cloud Monitoring Network Load Balancer Metric Details

Amazon Web Services Cloud Monitoring Gateway Load Balancer Metric Details

Amazon Web Services Cloud Monitoring Classic Load Balancer Metric Details

Application Load Balancer Metrics¶

The AWS/ApplicationELB namespace includes the following metrics for targets.

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

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

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

| Dimension | Description | || :----------------- | :------------------------------------------------------------------ | | AvailabilityZone | Filter metric data by availability zone. | | LoadBalancer | Filter metric data by load balancer. Specify the load balancer as follows: app/load-balancer-name/1234567890123456 (the ending part of the load balancer ARN). | | TargetGroup | Filter metric data by target group. Specify the target group as follows: targetgroup/target-group-name/1234567890123456 (the ending part of the target group ARN). |

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

Objects¶

The collected AWS ELB object data structure can be viewed 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: Fields in tags and fields may change with subsequent updates.

Tip 1: AWS ELB Metrics are divided into four types based on the type of load balancer:

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

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

1. For Classic Load Balancers, take the LoadBalancerName field.
2. For Application, Network, and Gateway Load Balancers, extract the ending part of the load balancer ARN (LoadBalancerArn).

Example for Network Load Balancer:

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

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

Tip 3:

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