AWS ELB¶

Use the[ Guance Synchronization] series script package in the script market to synchronize data from cloud monitoring cloud assets to the Guance.

config¶

Install Func¶

Recommend opening [ Integrations - Extension - DataFlux Func (Automata)] : All preconditions are installed automatically, Please continue with the script installation

If you deploy Func yourself,Refer to Self-Deployment of Func

Installation script¶

Tip: Please prepare AWS AK that meets the requirements in advance (For simplicity's sake, You can directly grant the global read-only permission for CloudWatch CloudWatchReadOnlyAccess)

To synchronize the monitoring data of AWS ELB cloud resources, we install the corresponding collection script :

AWS Application ELB select[Guance Integration ( AWS-ApplicationELBCollect )] (ID: guance_aws_applicationelb)

AWS Network ELB select[Guance Integration ( AWS-NetworkELBCollect )] (ID: guance_aws_networkelb)

AWS Gateway ELB select[Guance Integration ( AWS-GatewayELBCollect )] (ID: guance_aws_gatewayelb)

AWS Classic ELB select[Guance Integration ( AWS-ELBCollect )] (ID: guance_aws_elb)

Click [Install] and enter the corresponding parameters: AWS AK, AWS account name.

tap [Deploy startup Script] , The system automatically creates Startup script sets , And automatically configure the corresponding startup script.

Then, in the collection script, add the collector_configs and cloudwatch_change the regions in configs to the actual regions

After this function is enabled, you can view the automatic triggering configuration in[ Management / Crontab Config] . Click [ Run ] , you can immediately execute once, without waiting for a regular time. After a while, you can view task execution records and corresponding logs.

We collected some configurations by default, as described in the Metrics column Configure custom cloud object metrics

Verify¶

1. In[ Management / Crontab Config] check whether the automatic triggering configuration exists for the corresponding task,In addition, you can view task records and logs to check whether exceptions exist
2. On the Guance platform, click [Infrastructure / Custom] to check whether asset information exists
3. On the Guance platform, press [ Metrics] to check whether monitoring data exists

Metric¶

Configure AWS Cloud - cloud monitoring. The default metric set is as follows. You can collect more metrics by configuring them

AWS Application Load Balancer details

AWS Network Load Balancer details

AWS Gateway Load Balancer details

AWS Classic Load Balancer details

Application Load Balancer Metric¶

| ConsumedLCUs | The number of load balancer capacity units (LCU) used by your load balancer. You pay for the number of LCUs that you use per hour. For more information, see Elastic Load Balancing pricing.Reporting criteria: Always reported. Statistics: All. Dimensions: LoadBalancer |

| DesyncMitigationMode_NonCompliant_Request_Count | The number of requests that do not comply with RFC 7230. Reporting criteria: There is a nonzero value. Statistics: The most useful statistic is Sum. Dimensions: LoadBalancer, AvailabilityZone LoadBalancer |

| HTTPCode_ELB_3XX_Count | The number of HTTP 3XX redirection codes that originate from the load balancer. This count does not include response codes generated by targets. Reporting criteria: There is a nonzero value. Statistics: The only meaningful statistic is Sum. Dimensions: LoadBalancer,AvailabilityZone LoadBalancer |

| HTTPCode_ELB_4XX_Count | The number of HTTP 4XX client error codes that originate from the load balancer. This count does not include response codes generated by targets. Client errors are generated when requests are malformed or incomplete. These requests were not received by the target, other than in the case where the load balancer returns an HTTP 460 error code. This count does not include any response codes generated by the targets. Reporting criteria: There is a nonzero value. Statistics: The most useful statistic is Sum. Minimum, Maximum, and Average all return 1.Dimensions: LoadBalancer,AvailabilityZone LoadBalancer |

| HTTPCode_ELB_5XX_Count | The number of HTTP 5XX server error codes that originate from the load balancer. This count does not include any response codes generated by the targets. Reporting criteria: There is a nonzero value. Statistics: The most useful statistic is Sum. Minimum, Maximum, and Average all return 1.Dimensions: LoadBalancer,AvailabilityZone LoadBalancer |

| HTTPCode_ELB_500_Count | The number of HTTP 500 error codes that originate from the load balancer. Reporting criteria: There is a nonzero value. Statistics: The only meaningful statistic is Sum. Dimensions: LoadBalancer,AvailabilityZone LoadBalancer |

| HTTPCode_ELB_502_Count | The number of HTTP 502 error codes that originate from the load balancer. Reporting criteria: There is a nonzero value. Statistics: The only meaningful statistic is Sum. Dimensions: LoadBalancer,AvailabilityZone LoadBalancer |

| HTTPCode_ELB_503_Count | The number of HTTP 503 error codes that originate from the load balancer. Reporting criteria: There is a nonzero value. Statistics: The only meaningful statistic is Sum. Dimensions: LoadBalancer,AvailabilityZone LoadBalancer |

| HTTPCode_ELB_504_Count | The number of HTTP 504 error codes that originate from the load balancer. Reporting criteria: There is a nonzero value. Statistics: The only meaningful statistic is Sum. Dimensions: LoadBalancer,AvailabilityZone LoadBalancer |

| NewConnectionCount | The total number of new TCP connections established from clients to the load balancer and from the load balancer to targets. Reporting criteria: There is a nonzero value. Statistics: The most useful statistic is Sum. Dimensions: LoadBalancer,AvailabilityZone LoadBalancer |

| ProcessedBytes | The total number of bytes processed by the load balancer over IPv4 and IPv6 (HTTP header and HTTP payload). This count includes traffic to and from clients and Lambda functions, and traffic from an Identity Provider (IdP) if user authentication is enabled. Reporting criteria: There is a nonzero value. Statistics: The most useful statistic is Sum. Dimensions: LoadBalancer,AvailabilityZone LoadBalancer |

| RequestCount | The number of requests processed over IPv4 and IPv6. This metric is only incremented for requests where the load balancer node was able to choose a target. Requests that are rejected before a target is chosen are not reflected in this metric. Reporting criteria: Always reported. Statistics: The most useful statistic is Sum. Dimensions: LoadBalancer,AvailabilityZone LoadBalancer |

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.

Network Load Balancer Metric¶

Gateway Load Balancer Metric¶

Classic Load Balancer Metric¶

Metric for Application Load Balancers¶

To filter the metrics for your Application / Network / Gateway Load Balancer .

To filter the metrics for your Classic Load Balancer .

Object¶

The collected AWS ELB object data structure can be seen from the [ Infrastructure - Custom] object data

{
  "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}"
  }
}

Notice: tags,fieldsThe fields in this section may change with subsequent updates*

Remind 1: AWS ELB metric set is divided into four types according to different types of load balancing:

1. The index set of Application ELB is aws_aelb
2. The index set of Network ELB is aws_nelb
3. The index set of Gateway ELB is aws_gelb
4. The index set of Classic ELB is aws_elb

Remind 2: tags.name can be set in two ways:

1. Classic Load Balancers use the field of LoadBalancerName.
2. Application,Network,Gateway Load Balancers intercept the end of the load balancer ARN (LoadBalancerArn).

Take Network Load Balancer for example:

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

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

Remind 3:

• fields.message,tags.AvailabilityZones are post serialized character for JSON.
• tags.state means Load Balancers status,value:active,provisioning,active_impaired,failed (Classic ELB does not exist this field ).
• tags.Typemeans Load Balancers type,value:application,network,gateway,classic.
• tags.Schememeans Load Balancers mode,value:internet-facing,internal.
• fields.ListenerDescriptionsThis field is a list of listeners for the load balance.
• fields.AvailabilityZones This field indicates the Amazon Route 53 availability zone information associated with the load balancer.