[SERVER-49201] Add serverStatus metric for operation exceeded time limit Created: 30/Jun/20  Updated: 13/Nov/23  Resolved: 02/Sep/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.4.0-rc11
Fix Version/s: 7.2.0-rc0

Type: Improvement Priority: Minor - P4
Reporter: Kevin Arhelger Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: re-triaged-ticket, servicearch-metrics
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by COMPASS-7182 Investigate changes in SERVER-49201: ... Closed
Documented
is documented by DOCS-16363 [SERVER] Investigate changes in SERVE... Closed
Duplicate
is duplicated by SERVER-11243 Add server status counter "time limit... Closed
Related
related to SERVER-11243 Add server status counter "time limit... Closed
related to SERVER-49202 Add serverStatus metric for interrupt... Closed
Assigned Teams:
Service Arch
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0, v6.0, v5.0, v4.4
Sprint: Service Arch 2023-07-24, Service Arch 2023-08-07, Service Arch 2023-08-21, Service Arch 2023-09-04
Participants:

 Description   

Currently the only indicator of an operation breaching maxTimeMS is the timeout error returned in src/mongo/db/operation_context.cpp

A count of timed out operations may be diagnostically useful to determine application behavior.



 Comments   
Comment by Ana Meza [ 02/Nov/23 ]

Hi blake.oler@mongodb.com , wondering if SERVER-11243 is a duplicate of this?

Comment by Githook User [ 30/Aug/23 ]

Author:

{'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}

Message: SERVER-49201 Add serverStatus metric for operation exceeded time limit
Branch: master
https://github.com/mongodb/mongo/commit/4bec608bdfaca4f9e8e6dc5d30a7b00bba66f00e

Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ]

We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Generated at Thu Feb 08 05:19:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.