Events captured as part of the snapshot's history
Event | Data* | Who/What initiates it? |
---|---|---|
Snapshot Complete | alternateIds: ['id1', 'id2', 'id3',...] TODO: add snapshot-action: SNAPSHOT_COMPLETE method | Node |
Request Restore Snapshot | initiating-user: <user email> restore-action: RESTORE_REQUESTED | Bridge User |
Restore Initiated | restore-id: <restore-id> restore-action: RESTORE_INITIATED user-email: <request initiating user email> | Bridge Admin |
Restore Completed | restore-id: <restore-id> restore-action: RESTORE_COMPLETED expiration-date: yyyy-MM-dd | Bridge System |
Restore Expired | restore-id: <restore-id> restore-action: RESTORE_EXPIRED | Bridge System |
*All events have a date stamp associated with them.
Additionally, nodes can append node specific events to the snapshot history at any time via the /snapshot/{snapshot-id}/history REST call.
Events we should be capturing in history
Perhaps we should be capturing all state transitions as part of the history?
Event | Data | Who/What Initiates It |
---|---|---|
Transfer to Bridge Complete | Bridge System | |
Transfer to Bridge Failed | Bridge System | |
Verification of DuraCloud to Bridge transfer succeeded | Bridge System | |
Verification of DuraCloud to Bridge transfer failed | Bridge System | |
Transfer to DPN failed | DPN Node | |
Transfer from DPN succeeded | DPN Node | |
Transfer to DuraCloud failed | Bridge System | |
Transfer to DuraCloud succeeded | Bridge System | |
Verification of DPN to bridge transfer succeeded | Bridge System | |
Verification of DPN to bridge transfer failed | Bridge System | |
Verification of Bridge to DuraCloud transfer succeeded | Bridge System | |
Verification of Bridge to DuraCloud transfer succeeded | Bridge System |