🐛 Sync critical issues badge with actual data#12972
Conversation
The DashboardHealthIndicator badge was counting backend disconnection as a critical issue even in demo mode, where disconnection is the expected state. This created a contradiction: badge shows 'X critical issues' while page stat cards show '0 critical' because they count from actual data sources. Now backend disconnection is only counted as critical when: - Not in demo mode (disconnection is unexpected) - Agent was previously connected (user had connectivity and lost it) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Copilot <copilot@github.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Deploy Preview for kubestellarconsole ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
👋 Hey @kubestellar-hive[bot] — thanks for opening this PR!
This is an automated message. |
Use page-specific header badges on Insights and Clusters so the header reflects the same source as each page's stats. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Copilot <copilot@github.com>
|
Thank you for your contribution! Your PR has been merged. Check out what's new:
Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey |
|
Post-merge build verification passed ✅ Both Go and frontend builds compiled successfully against merge commit |
✅ Post-Merge Verification: passedCommit: |
Fixes #12971
The critical issues badge in the page header was showing a count that did not match the Critical stat card. This fix ensures both use the same data source.
Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com