Incorrect description for aws.applicationelb.request_count: metric does include HTTP 460

Open Beginner friendly
#36,762 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
aws
Domain
documentation

Research direction

Find the documentation source entry for the aws.applicationelb.request_count metric and compare its description with the linked AWS CloudWatch ALB metrics documentation. Correct the description so it no longer incorrectly excludes HTTP 460, then verify that the rendered metric text reflects the AWS definition.

Written by the indexing model from the issue text.

Description

Bug

aws.applicationelb.request_count description says:

"Not inclusive of HTTP 460, HTTP 400, and some kinds of HTTP 503 and 500."

The HTTP 460 exclusion claim appears incorrect.

AWS docs deduction

From CloudWatch ALB metrics:

  • RequestCount: "only incremented for requests where the load balancer node was able to choose a target"
  • HTTPCode_ELB_4XX_Count: "These requests were not received by the target, other than in the case where the load balancer returns an HTTP 460 error code."

460 means the client closed after the ALB routed to a target. A target was chosen. The AWS definition implies it counts in RequestCount.

Dominant language
JavaScript
Stars
618
Forks
1.3k
Avg merge
2d 5h
Merged PRs (30d)
471

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DataDog/documentation

All issues in DataDog/documentation

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.