Conversation
System Settings > Log Settings: - Add a warning to Enable Log Rotate After explaining this is new in 2608. Earlier server versions kept Device Control, Content Aware Protection, and eDiscovery logs indefinitely with no automatic deletion; 2608 enables three-month rotation by default on migration. Recommend reviewing the value and using Export Logs to preserve compliance evidence separately. Migration guides (both legacy 5.x and current-image paths): - Add a Log Retention Verification step to Post-Migration Verification, before Audit Log Backup Verification, prompting admins to check and configure Enable Log Rotate After post-migration. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- Merge the two stacked log rotation warnings in System Settings into one, open with the behavior change, explain the Audit Log Backup side effect, and state that logs already past the retention period are deleted on the first rotation cycle within five minutes of startup - Move Log Retention Verification ahead of Third-Party Integration Reconfiguration in both migration guides so it's reached before rotation runs - Add the first-rotation-cycle warning, the units and disable value, and a link to the Log Settings reference in both migration guides - Replace the vague export rationale with the performance benefit - Use the arrow separator consistently in the migration guides and reconcile the menu name to Reports and Analysis Co-Authored-By: Claude <noreply@anthropic.com>
…ion warnings - Audit Log Backup deletion is an option, not automatic: System Maintenance documents a per-job choice of whether to keep or delete logs from the server, so 'archives logs off the server and clears them from the database' overstates it - Make the first-rotation-cycle sentence active per the Netwrix voice rules, and restore the actionable 'export before you migrate' guidance in both guides Co-Authored-By: Claude <noreply@anthropic.com>
Flagged by Flaviu: the setting can't actually be set to 0. Confirmed in code (configure/actions.class.php) that the save handler requires 1-360; PHP's empty(0) check means 0 is silently rejected with no error shown, so there's no supported way to fully disable log rotation once Communication V2/CrateDB is active — 1 month is the minimum. Corrects the same false claim in three places: the Log Settings bullet and warning in systemsettings.md, and the identical Log Retention Verification step duplicated across both migration guides. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Document EPP 2608 automatic log rotation as a behavior change
Add a RHEL and CentOS Preparation section covering the kernel-modules-extra package RHEL 10 needs, firewalld rules (or disabling it), and the NetworkManager/nm-cloud-setup bug on RHEL/CentOS releases before 8.4. Sourced from https://docs.k3s.io/installation/requirements#operating-systems, scoped to what applies to Access Analyzer's single-node install. Update requirements.md's OS row to mention RHEL/RPM-based support and link to the new section, since it previously implied only Debian-based distributions were supported.
Document RHEL and CentOS installer prep steps
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.