Summary
Currently, "Observe Only" repositories have limited visibility within the UI. While some data is available in the Archives section, these repositories are missing from key global views like the Dashboard and Activity feeds.
The goal is to integrate "Observe Only" repositories into the general monitoring flow to provide a unified status of all managed backups.
Description
The primary motivation for this request is a network environment where a central server receives backups from multiple remote nodes. Even though these repositories are configured as 'observe only' on the local interface, it is essential to integrate them into the global monitoring flow. This would allow supervising the backup status across the entire infrastructure from a single dashboard, ensuring all remote servers are completing their backup cycles correctly.
Proposed Changes
1. Dashboard section
- Repository Health: Include "Observe Only" repos in the health status summary.
- Recent Activity: Show the most recent snapshots or sync events from these repositories.
- Upcoming & Maintenance: If there are scheduled consistency checks they should appear in the upcoming tasks list.
2. Activity section
- Incorporate events related to "Observe Only" repositories so users can track sync history alongside regular backup sets.
3. Backup section
- Display history of backup operations for these repositories to ensure the "observation" is up to date.
Technical Context
- Current State: Data for these repositories is already being fetched/displayed in the Archives section.
- Feasibility: The underlying data structures seem to exist; the request focuses on surfacing this data in the global components mentioned above.
Summary
Currently, "Observe Only" repositories have limited visibility within the UI. While some data is available in the Archives section, these repositories are missing from key global views like the Dashboard and Activity feeds.
The goal is to integrate "Observe Only" repositories into the general monitoring flow to provide a unified status of all managed backups.
Description
The primary motivation for this request is a network environment where a central server receives backups from multiple remote nodes. Even though these repositories are configured as 'observe only' on the local interface, it is essential to integrate them into the global monitoring flow. This would allow supervising the backup status across the entire infrastructure from a single dashboard, ensuring all remote servers are completing their backup cycles correctly.
Proposed Changes
1. Dashboard section
2. Activity section
3. Backup section
Technical Context