[SERVER-36690] Add advisoryHostFQDNs to Free Monitoring metrics payloads Created: 15/Aug/18 Updated: 06/Dec/22 Resolved: 22/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Duncan Armstrong | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | sa-groomed | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Service Arch
|
||||
| Participants: | |||||
| Description |
|
If feasible, could we please include advisoryHostFQDNs in the serverStatus in the metrics payload? |
| Comments |
| Comment by Duncan Armstrong [ 15/Sep/18 ] |
|
Yup, both would be ideal |
| Comment by Andrew Morrow (Inactive) [ 21/Aug/18 ] |
|
As will always be the case with advisoryHostFQDNs, I'm reluctant to expand its scope. It is information that is known to be potentially inaccurate or not meaningfully interpretable, and was added to enable a very specific set of use cases. Without an extremely strong motivation put forward, I'm disinclined to surface this information through new/additional channels. Can you please explain in detail why you want this, and why this is the only way to achieve that aim? |