[SERVER-30248] Auditing should contain logical clock information to allow ordering of distributed events Created: 20/Jul/17 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Osmar Olivo | Assignee: | Backlog - Security Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | Auditing, auditing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Security
|
| Sprint: | Sharding 2018-07-30, Sharding 2018-08-13 |
| Participants: |
| Description |
|
When querying or walking through the audit trail, it is difficult to determine in which order certain events occured because timestamps may not always be accurate. Providing a means to allow for logical ordering of distributed log events would be useful. |
| Comments |
| Comment by Kaloian Manassiev [ 28/Jul/17 ] |
|
Assigning to misha.tyulenev so he and osmar.olivo can work out what this information should look like. We might not have time to put it in for the 3.6 release, but it might be able to go out in a 'dot' release after that. |