[SERVER-38104] serverStatus metrics for currently in-progress ops/commands Created: 13/Nov/18  Updated: 06/Dec/22  Resolved: 15/Nov/18

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Backlog - Service Architecture
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-38068 Track successful command completion i... Backlog
Related
related to SERVER-34422 Expose metrics on idle versus active ... Closed
Assigned Teams:
Service Arch
Participants:

 Description   

Current serverStatus/FTDC metrics focus on the receipt of a request to do some unit of work, eg. opcounters increment when the operation is received, command metrics increment when the command id dispatched (and then again if it fails).

However there are many situations where it is vital to know how much work is currently in-progress on the server, ie. of the ops/commands received so far, how many have been completed?

In addition to the work on SERVER-34422 (which would enable a very coarse view of "fraction of client threads that are currently doing 'stuff'"), it would be extremely useful if there were metrics for each opcounter and command metric that get incremented immediately after the operation/command completes. This would allow the number of currently active/in-progress ops/commands to be easily computed by subtracting these "completed" metrics from the regular "started" metrics. (It could also enable interesting visualisations like burn-down charts for ops/commands.)

Logging is not a viable workaround, because it is focussed on work completion, and although higher log levels show when operations/commands start, this cannot be enabled retrospectively, and usually not enabled permanently (since it tends to cause excessively high logging rates).



 Comments   
Comment by Kevin Pulo [ 15/Nov/18 ]

Apologies, yes, it is.

Comment by Bruce Lucas (Inactive) [ 14/Nov/18 ]

This sounds like the same request as SERVER-38068? Note that I have some concern on that ticket regarding the number of new metrics that this would introduce.

Generated at Thu Feb 08 04:47:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.