[SERVER-69831] Report on metrics gathered in the SessionWorkflow loop Created: 20/Sep/22 Updated: 02/Nov/22 Resolved: 26/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matt Diener (Inactive) | Assignee: | Matt Diener (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | diagnostics | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||||||||||
| Sprint: | Service Arch 2022-10-03, Service Arch 2022-10-17, Service Arch 2022-10-31 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 105 | ||||||||||||||||||||||||||||
| Description |
|
Context: Previous task: ( This task: Report on these gathered metrics in a manner that's satisfactory to the requirements of stakeholders of the original tickets: Requirements should be discussed with bruce.lucas@mongodb.com. |
| Comments |
| Comment by Githook User [ 20/Oct/22 ] |
|
Author: {'name': 'Matt Diener', 'email': 'matt.diener@mongodb.com', 'username': 'mattdiener'}Message: |
| Comment by Matt Diener (Inactive) [ 27/Sep/22 ] |
|
I have reason to believe that tracking all connections as they move through these states at this granularity will likely introduce some performance degradations that we don't want to take on, whereas a count of outliers is less likely to cause those problems. At that point FTDC doesn't seem much better than logging, from my perspective. The biggest question from my perspective pertains to configurability, and determining the threshold for "slow". Can we use the same time threshold as slow queries or is there a reasonable case to be made for adding a 2nd value that can be configured? I'm content if we use our best judgement for the rest. |
| Comment by Bruce Lucas (Inactive) [ 27/Sep/22 ] |
|
matt.diener@mongodb.com regarding the log lines, I think you're asking about the relative merits of a couple of design alternatives, but I can't quite follow what the alternatives are. Can you give a couple short examples of the alternatives to clarify? Generally speaking, I think the requirement is to log when sending a response (or receiving a request, I think) is slow, as this causes the client to see a slow response, whereas given the current logging we don't see any indication of that slowness. Ideally it should be possible to tie this slow response back to details of the query in some way. I Regarding FTDC, I think it would be useful to have some information in FTDC. Generally the kind of information that's useful is number of connections in a particular state, and/or cumulative time spent between particular state transitions. I think there was some discussion in the design doc regarding some useful metrics of this type. I'm not sure what metrics you have in mind to replace.
|
| Comment by Matt Diener (Inactive) [ 21/Sep/22 ] |
|
bruce.lucas@mongodb.com – some detailed questions that were not answered in the design:
|