[SERVER-36826] Report setting of FCV in logs and diagnostics Created: 23/Aug/18 Updated: 06/Dec/22 Resolved: 10/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Logging |
| Affects Version/s: | None |
| Fix Version/s: | 4.3 Desired |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Mark Brinsmead | Assignee: | Backlog - Service Architecture |
| Resolution: | Duplicate | Votes: | 19 |
| Labels: | move-sec, neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
The current value of featureCompatibiliyVersion should be reported with other parameters in FTDC diagnostics and logfiles, as this can be helpful diagnostic information. Startup warnings alerting users that not all features are available because FCV does not match the current software release may also be helpful. |
| Comments |
| Comment by Blake Oler [ 10/Dec/21 ] |
|
Closing as duplicate of linked tickets. |
| Comment by Kaloian Manassiev [ 24/May/19 ] |
|
Passing this on to Query since they are picking-up FCV in 4.4. |
| Comment by Randolph Tan [ 05/Sep/18 ] |
|
What we currently have is log during changes: I don't think we currently don't log the current FCV on startup. |
| Comment by Kaloian Manassiev [ 04/Sep/18 ] |
|
renctan, claims that we already do that. Assigning to him to verify. |
| Comment by Bruce Lucas (Inactive) [ 23/Aug/18 ] |
|
I think it would be useful to log this on every log rotation, like we do with db version currently. |