Skip to main content

Triage Check AWS Classic Load Balancer Low Traffic LOW_BYTES_PROCESSED

  1. Configure Check AWS Classic Load Balancer Low Traffic
  2. Use Case for Check AWS Classic Load Balancer Low Traffic
  3. Triage Guides by Violation Type
    1. Triage Check AWS Classic Load Balancer Low Traffic LOW_BYTES_PROCESSED

Understanding Low Bytes Processed Violation

Understand​

Why should I care about fixing this issue?

  • An AWS Classic Load Balancer with low traffic may indicate unused resources, leading to unnecessary costs.

Validate​

How can I be sure this alert is accurate?

  • The data source for this policy is CloudWatch metrics, specifically EstimatedProcessedBytes. Retrieve it manually using AWS CloudWatch console or CLI to cross-reference. Is this policy reactive?
  • No, it runs daily.

Triage​

What if it remains unfixed?

  • Continual low usage can result in ongoing costs without business value. However, it likely does not affect running services directly. Can remediation cause outages?
  • Addressing this issue should not cause outages.

Act​

What do I do to fix this alarm?

  • Investigate load balancer usage patterns. Consider scaling down or reconfiguring as needed.

Reflect​

How to adjust if the alarm wasn't useful?

  • Review and adjust bytesPerDayThreshold and daysToCheck variables to better match expected traffic.