[SERVER-35501] Add payload timestamp to Free Monitoring Register and Metrics request payloads Created: 07/Jun/18 Updated: 29/Oct/23 Resolved: 11/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc5, 4.1.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Duncan Armstrong | Assignee: | Mark Benvenuto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.0
|
||||
| Sprint: | Platforms 2018-06-18 | ||||
| Participants: | |||||
| Description |
|
To facilitate accounting for clock skew between mongods and the Free Monitoring application server, we need a timestamp at the payload level, recording the time when the payload envelope was created (i.e. as close to making the POST request as possible). Without it, we have to rely on timestamps from the payload contents, which may have been collected some time prior to the POST being sent. |
| Comments |
| Comment by Githook User [ 12/Jun/18 ] |
|
Author: {'username': 'markbenvenuto', 'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com'}Message: (cherry picked from commit 8c5fd63e89fc03d98d229d818cf610a46426b3b7) |
| Comment by Githook User [ 11/Jun/18 ] |
|
Author: {'username': 'markbenvenuto', 'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com'}Message: |