Skip to main content

Triage GWLB Low Usage Detector LOW_BYTES_PROCESSED

  1. Configure GWLB Low Usage Detector
  2. Use Case for GWLB Low Usage Detector
  3. Triage Guides by Violation Type
    1. Triage GWLB Low Usage Detector LOW_BYTES_PROCESSED

LOW_BYTES_PROCESSED Violation Guide​

Understanding why this GWLB has unusually low bytes processed is crucial for maintaining cost-effective infrastructure.

To validate this alert, review the processed bytes CloudWatch metrics for the GWLB. These metrics are retrieved via a CloudWatch GET request, averaged over the past N days set by a variable (default 30). The policy scans reactively to reported metrics.

The impact of not addressing this issue is primarily financial, as it may indicate an overprovisioned and underutilized resource. Over time, if genuine traffic is consistently low, consider downsizing the GWLB.

To act on this alert, investigate the GWLB traffic and adjust its capacity or configuration appropriately.

If this alarm is frequent and not beneficial, consider adjusting the byteThreshold variable or investigating the expected usage pattern of the GWLB.