fix(aws_elb_metrics_otel): filter TargetGroup/AvailabilityZone rollup… - #20870
fix(aws_elb_metrics_otel): filter TargetGroup/AvailabilityZone rollup…#20870mrg-elastic wants to merge 6 commits into
Conversation
… rows to prevent metric overcounting
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
|
nit: Example: Single metric panel, Detailed dashboard |
|
Detailed dashboard / Account ID: |
…shboard 14 panels were missing TargetGroup IS NULL and/or AvailabilityZone IS NULL, causing ~95% overcounting from CloudWatch multi-dimension rollup duplicates. All metric panels in the overview now filter to load-balancer-level granularity.
…im-filtering Three classes of fixes across ALB, NLB, and GWLB detail dashboards: 1. HealthyHostCount / UnHealthyHostCount: remove TargetGroup IS NULL — these metrics are only published at the LoadBalancer+TargetGroup dimension level, never at LoadBalancer-only, so the filter emptied all 12 panels in ALB/NLB. 2. Backend 5XX error rate card (ALB): remove RequestCount IS NOT NULL pre-filter from WHERE — it excluded 5XX documents causing the aggregation to always return 0. Both metrics now use CASE(stat == "Sum", metric, NULL) inside STATS. 3. Aggregation dimension filtering: move stat == "X" pre-filter from WHERE into CASE(stat == "X", metric, NULL) inside every *_over_time() and raw STATS aggregation, making it explicit which CloudWatch statistic contributes to each data point and preventing future double-counting if new stat types are added.
|
Panel title: Active connections over time (sum) Qn? Do you want to consider removing the suffix Do you want to consider |
|
Panel name : Primary metric: Browse other AWS OTel dashboards |
|
Every NLB detail panel queries the ALB stream metrics-aws.elb.otel-. You may have to retarget them to metrics-aws.elb_network.otel- and the matching dataset. Please check for the gateway load balancer. This has an impact on the Overview dashboards, as these are different datasets - the data shown in the Overview dashboard (count, table view, hexmap) presently is ALB specific, might not be covering other LB types. So, you may have to revisit the Overview dashboard as well. |
|
ELB - NLB Details dashboard
Please add the stat == "Sum"
|
…ta streams and expand overview to all ELB types
… and GWLB detail dashboards
|
✅ All changelog entries have the correct PR link. |
💚 Build Succeeded
History
|



… rows to prevent metric overcounting
Proposed commit message
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots