|Applies To||In SilverTail version 4.0, the merge of schema attributes in a single location added dictionaries from the user-mapping for Mitigator to maintain.|
|Issue||What is Schema.Mitigator.pruneAttributes in SilverTail v4.x|
|Resolution||Some of these attributes can changes often (like rotating sessionIDs). |
This caused Mitigator memory usage to appear unbounded and can easily exceeded available physical memory.
To mitigate this, a new feature pruneAttributes was introduced.
The decision to determine which attributes to add to this setting can be based on the following set of guidelines.
a) You cannot prune attributes that are used in schema.keys or used in mitigator rules (in the rule itself or in the incident details).
b) You cannot prune attributes if other required attributes depend on it.
c) Default attributes like guid-out, next-guid, prev-guid-out and user attributes used in login page definitions (like: user-from-login) can be prune
|Legacy Article ID||a61772|