hippogrief/pobsync
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Clarify or enable rsync progress output in live run views #64

New Issue
Closed
opened 2026-05-23 02:23:31 +02:00 by parkel · 0 comments
parkel commented 2026-05-23 02:23:31 +02:00
Owner
Copy Link

Problem

Now that dry-runs and real backup runs have live log views, the run detail page can look stalled when rsync is still active but no progress output is emitted. In practice the live view currently shows SSH warnings and rsync errors, but not ongoing transfer progress unless rsync is configured to emit it.

Options to evaluate

  • Enable rsync progress output by default for interactive visibility, for example via a safe --info=progress2 or related option.
  • Keep default rsync output quiet, but make the UI explicit that live logs only show warnings/errors unless verbose/progress output is enabled.
  • Add a per-run or global toggle for progress verbosity so long-running backups are easier to inspect without forcing noisy logs everywhere.

Acceptance criteria

  • Operators can understand whether a running backup is quiet-by-design or actually stalled.
  • The live run view communicates rsync progress behavior clearly.
  • If progress output is enabled, it should not break stats parsing or flood stored logs excessively.
## Problem Now that dry-runs and real backup runs have live log views, the run detail page can look stalled when rsync is still active but no progress output is emitted. In practice the live view currently shows SSH warnings and rsync errors, but not ongoing transfer progress unless rsync is configured to emit it. ## Options to evaluate - Enable rsync progress output by default for interactive visibility, for example via a safe `--info=progress2` or related option. - Keep default rsync output quiet, but make the UI explicit that live logs only show warnings/errors unless verbose/progress output is enabled. - Add a per-run or global toggle for progress verbosity so long-running backups are easier to inspect without forcing noisy logs everywhere. ## Acceptance criteria - Operators can understand whether a running backup is quiet-by-design or actually stalled. - The live run view communicates rsync progress behavior clearly. - If progress output is enabled, it should not break stats parsing or flood stored logs excessively.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: future
Longer-term product direction.
 area: observability
Metrics, history, and capacity insights.
 area: policy
Backup policies, templates, and automation.
 area: restore
Restore and recovery workflows.
 area: security
Permissions, audit, and security hardening.
 bugfix
Bug fixes and correctness work.
 docs
Documentation and operator guidance.
 feature
New functionality.
 refactor
Internal restructuring without direct behavior changes.
 release
Release preparation and publishing.
 security
Security, permissions, and audit work.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
parkel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hippogrief/pobsync#64
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?