Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a replication log analysis tool for performance monitoring #6465

Open
droideck opened this issue Dec 31, 2024 · 0 comments · May be fixed by #6466
Open

Add a replication log analysis tool for performance monitoring #6465

droideck opened this issue Dec 31, 2024 · 0 comments · May be fixed by #6466
Labels
needs triage The issue will be triaged during scrum

Comments

@droideck
Copy link
Member

Description
Add a new ReplicationLogAnalyzer class and supporting infrastructure to analyze replication performance across multiple servers. The tool parses replication logs, tracks CSNs, calculates lag times, and generates comprehensive reports in multiple formats including interactive HTML visualizations.
Additionally, add CLI and UI implementations.

Implementation References
Base implementation can be adapted from: https://github.com/droideck/ansible-ds389-repl-monitoring/tree/main/roles/ds389_repl_monitoring/library

@droideck droideck added the needs triage The issue will be triaged during scrum label Dec 31, 2024
droideck added a commit to droideck/389-ds-base that referenced this issue Jan 20, 2025
Description: Add a new ReplicationLogAnalyzer class and supporting infrastructure
to analyze replication performance across multiple servers. The tool parses
replication logs, tracks CSNs, calculates lag times, and generates comprehensive
reports in interactive HTML and CSV formats.

Based on: https://github.com/droideck/ansible-ds389-repl-monitoring

Fixes: 389ds#6465

Reviewed by: ?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage The issue will be triaged during scrum
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant