User story #4438
closed
Proposal: List of non-compliant hosts on dashboard
Added by Dennis Cabooter almost 11 years ago. Updated over 7 years ago.
Description
It would be nice to have a "non compliant hosts" report on the dashboard. In that way, I don't have to walk through all rules every day to find out which hosts are non-compliant (and why).
Updated by François ARMAND almost 11 years ago
Ah, yes. A little like Rudder was a compliance-checking tool, and we didn't put compliance report on the front page ?
Updated by François ARMAND almost 10 years ago
- Category set to Web - UI & UX
- Target version set to 3.1.0~beta1
I'm requalifying / retargetting that one now that in 3.0, we have an actual dashboard.
With that dashboard, it seems that the lower left chart wants to be clickable and on click, open the list of nodes, filtered to only have the one with the matching compliance.
And in fact, I believe that we want the compliance and recent changes that appears in rule grid on list of nodes, to.
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 3.1.0~beta1 to 3.1.0~rc1
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 3.1.0~rc1 to 3.1.0
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 3.1.0 to 3.1.1
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 3.1.1 to 3.1.2
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.1.2 to 3.1.3
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.1.3 to 3.1.4
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.1.4 to 3.1.5
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 3.1.5 to 3.1.6
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 3.1.6 to 3.1.7
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.7 to 3.1.8
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.8 to 3.1.9
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.9 to 3.1.10
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.10 to 3.1.11
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.11 to 3.1.12
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.12 to 3.1.13
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.13 to 3.1.14
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Alexis Mousset about 8 years ago
- Tracker changed from Bug to User story
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by Benoît PECCATTE over 7 years ago
- Status changed from New to Rejected
This is solved by the compliance available in nodes list (see #6781)
Updated by Benoît PECCATTE over 7 years ago
- Related to User story #6781: Display node compliances in Nodes lists added