Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

551
Views
AWS Application Load balancer - HTTPCode_ELB_4XX_Count vs HTTPCode_Target_4XX_Count?

What is the actual difference between HTTPCode_ELB_4XX_Count and HTTPCode_Target_4XX_Count?

Could understand that HTTPCode_ELB_4XX_Count is based on http code returned by ELB and HTTPCode_Target_4XX_Count is based on http code returned by target. Still not able to understand how to analyze and troubleshoot the count for each metrics?

Is this count depended on health check failure?

over 4 years ago · Santiago Trujillo
2 answers
Answer question

0

Based on the doc: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-cloudwatch-metrics.html

The answer above seems wrong, should be:

  • HTTPCode_ELB_4XX_Count - This is the number of 4XX errors that are returned from the ELB.
  • HTTPCode_Target_4XX_Count - This is simply a 4XX error returned from the application servers.
over 4 years ago · Santiago Trujillo Report

0

These are 2 metrics used to help diagnose where the fault lies for ay 4XX errors.

  • HTTPCode_ELB_4XX_Count - This is simply a 4XX error returned from the application servers.
  • HTTPCode_Target_4XX_Count - This is the number of 4XX errors that are returned from the ELB.

To get a gauge of what can trigger this take a look at this page for a list of HTTP statuses mapped to the cause of the ELB error.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!