Bug #13429
closed
Make nodecompliance ttl data
Description
Related to #13427.
We need to be able to limit drasticly the size of "nodecompliance" table. That table is used for logging the compliance of all nodes at a very precise level but rudder can works without it.
So, user should be able to disable that table if they want, or at least control its ttl at hour level.
Today, the ttl of that data is linked to ttl or report archiving. So we need to split that property appart.
Updated by François ARMAND over 6 years ago
- Target version changed from 4.1.15 to 4.3.5
- Effort required changed from Very Small to Small
- Priority changed from 94 to 80
There was significant code changes between 4.1 and 4.3 and I'm not at all confident about doing any changes in 4.1 in that part - even in 4.3, it may not be trivial.
Updated by François ARMAND over 6 years ago
- Status changed from In progress to New
- Assignee deleted (
François ARMAND) - Effort required changed from Small to Medium
- Priority changed from 80 to 48
So, the code is not that simple to change. It need more work than thought, evec in 4.3.
The reason is that we only have one scheduler for that, and that that TTL would need to live in an other to go below day atomicity. That means an other display, etc.
But it also need code to deal differently with the "0" case, because for that one, we want 0 to mean "don't log at all", not "don't clean at all".
So actually, we need 0 to do a "truncate" or similar if table non-empty, but ALSO to have a check in report processing which don't log at all nodecompliance in that case.
So... All that is needs a couple of days to be taken care of in a released version.
Updated by
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.3.14 to 5.0.13
It may have already been done in 5.0.12, retargeting to 5.0 and asking people who knows!!
Updated by Nicolas CHARLES about 5 years ago
- Status changed from New to Rejected
compliance has its own ttl now