[COMPASS-423] Use $comment for all write operations originating in Compass Created: 23/Nov/16 Updated: 25/Sep/18 Resolved: 25/Sep/18 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Thomas Rueckstiess | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Epic Link: | COMPASS-2239 | ||||
| Description |
|
This will help users going through log files and/or audit logs to identify operations that were executed with Compass. This would be helpful to undo any unintentional updates introduced for example via COMPASS-331. |
| Comments |
| Comment by Thomas Rueckstiess [ 07/Aug/17 ] |
|
Now that we have Client Meta Data identification, this is not quite as urgent anymore, but it's still a value-add as the client meta data is only visible when the connection is established, but not for ongoing queries. In support, where customers send log file snippets, it's often the case that the connection start happened earlier and is not part of the log file, so having a $comment for each request is still helpful. |