User story #5297
closedUser story #5293: Add a 'changes only' compliance mode, only reporting changes on systems
Adapt display to handle new compliance/change only mode
Description
When in non compliance mode, we must:
- inform the user of the situation,
- display success when needed,
- display last execution time (not mandatory for now).
The main idea for modification are:
In the rule grid:
- compliance is displayed as a "stacked progress bar", with colors for each state
- success, repaired, not applicable are ALL green/success (rationnal: in all case, it's OK for these status)
- we must display a chart with the list of last changes for each rule.
For the graph part, a default period of 30 days of changes, plus the possibility to zoom on some sub-interval, seems OK.
We can look at the following graph libraries: http://dygraphs.com/gallery and http://www.chartjs.org/
Color code for the status bar and order of elements:
- Not applicable: green (different one ?)
- Success: green (different one ?)
- Repaired: green (different one ?)
- Error: Red
- Applying: Blue with strikes
- No reports: Orange (light)
- Unexpected / Missing: Orange (strong)
For a Rule details:
For compliance reports, change the current reporting by directive/components etc to have 3 view:
- the same as now (for the rule, directive/component/etc)
- a view by node (with for each node, direcitve/components/etc)
- a view with the list of all changes, in a table with Date/node id/directive/component/value/messages.
Updated by François ARMAND over 10 years ago
- Project changed from 34 to Rudder
- Parent task deleted (
#5293)
Updated by François ARMAND about 10 years ago
- Subject changed from Adapt display to handle "non compliance" mode to Adapt display to handle new compliance/change only mode
- Description updated (diff)
- Assignee deleted (
François ARMAND)
Updated by Matthieu CERDA about 10 years ago
- Target version changed from 140 to 3.0.0~beta1
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from 8 to Pending release
- % Done changed from 0 to 100
Applied in changeset 31211348982d141c390659bdcc66dda140365a60.
Updated by François ARMAND about 10 years ago
Applied in changeset 4e26b9448ccf2ed6fe6458d08e9ca14168b8d6f6.
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta1 which was release on 01/12/2014.
- Announcement
- Changelog
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Benoît PECCATTE over 9 years ago
- Tracker changed from Enhancement to User story