[Bug] Score inconsistencies between Dashboard and “WAF Recommendations (Not Met)” page

[albertwangnz]

Description

When using the Databricks-WAF-Light-Tooling dashboards, I noticed several score inconsistencies between the Dashboard view and the “WAF Recommendations (Not Met)” page.

These inconsistencies make it difficult to understand the actual compliance status of certain Well-Architected Framework (WAF) checks.

Observed behavior

1. Score mismatch for the same recommendation

• PE-02-06 – Design workloads for performance – Use native platform engines
  • On the Dashboard, the score is shown as 91
  • On the “WAF Recommendations (Not Met)” page, the score for the same item is shown as 71.3%

2. Items showing 0 score on Dashboard but missing from “Not Met” page

The following two recommendations both show a score of 0 on the Dashboard:

• PE-02-05 – Design workloads for performance – Use native Spark operations
• PE-02-07 – Design workloads for performance – Understand your hardware and workload type

However, neither of these items appears on the “WAF Recommendations (Not Met)” page, which seems to imply that they are considered “Met”, despite having a score of 0 on the Dashboard.

Expected behavior

• Scores for the same WAF recommendation should be consistent across all dashboards and recommendation pages
• Recommendations with a score of 0 should clearly appear under “WAF Recommendations (Not Met)”, or the Dashboard should clarify why they are treated as “Met”
• The scoring logic and thresholds should be applied and presented consistently to avoid confusion

Impact

These inconsistencies can lead to:

• Confusion when interpreting WAF compliance results
• Difficulty prioritizing remediation work
• Reduced trust in the accuracy of the scoring output

[albertwangnz]

From: Abhishek Pratap Singh

1. Score inconsistency (PE-02-06: 91 vs 71.3%)
   Root cause found: the Lakeview dashboard was running live queries against system tables at view time, while the app was reading from a cached snapshot. They were never looking at the same data. We are aligning both to always read from the same snapshot so scores will be consistent going forward.

2. PE-02-05 / PE-02-07 showing 0 but absent from "Not Met" page
   These controls had incomplete scoring logic. PE-02-05 had no score computation at all (informational only), and PE-02-07 was using an incorrect formula.