Events captured by the Bridge as part of the snapshot's history (CURRENT)
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 |
...
Additionally, nodes can append node specific events to the snapshot history at any time via the /snapshot/{snapshot-id}/history REST call.
Actions we should be capturing in snapshot history
...
(TO DO)
Event | Data* | Who/What initiates it? |
---|---|---|
Snapshot Initiated |
| Bridge |
Snapshot Transfer to Chronopolis Complete |
| Bridge |
Snapshot Replication to DPN Nodes |
| Intake Service |
Snapshot Complete |
| Intake Service |
...
Bridge status events which are not captured in snapshot history
...