[SERVER-76631] Store CPU model name in FTDC metadata Created: 27/Apr/23 Updated: 29/Oct/23 Resolved: 24/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.0.5 |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kevin Arhelger | Assignee: | Brad Moore |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Security
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Security 2023-05-15, Security 2023-05-29, Security 2023-06-12, Security 2023-06-26 | ||||
| Participants: | |||||
| Description |
|
While CPU frequency, core count, etc. are currently included in FTDC, its sometimes difficult to understand what generation, turbo frequency, etc a given host may be simply from FTDC. The "model name" field from /proc/cpuinfo would aid investigations, especially of mixed configuration replica sets. |
| Comments |
| Comment by Githook User [ 14/Jun/23 ] |
|
Author: {'name': 'W. Brad Moore', 'email': 'brad.moore@mongodb.com', 'username': 'wbradmoore'}Message: |
| Comment by Kelsey Schubert [ 11/May/23 ] |
|
I think if we can put it into hostInfo that'd fit the bill. |