[SERVER-44689] Add serverStatus counter for each use of an aggregation stage in a user's request Created: 18/Nov/19  Updated: 08/Nov/23  Resolved: 20/Feb/20

Status: Closed
Project: Core Server
Component/s: Aggregation Framework, Diagnostics
Affects Version/s: None
Fix Version/s: 4.2.6, 4.3.4, 4.0.19

Type: Improvement Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Mihai Andrei
Resolution: Fixed Votes: 0
Labels: qexec-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Documented
is documented by DOCS-13435 Investigate changes in SERVER-44689: ... Closed
Related
related to SERVER-82928 Reconsider mongos approach to only in... In Progress
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2, v4.0, v3.6
Sprint: Query 2020-01-13, Query 2020-01-27, Query 2020-02-10, Query 2020-02-24
Participants:

 Description   

Similar to the way in which MongoDB exports counters for the number of times each command executes, it should export a counter indicating how often each unique aggregation pipeline stage that appears in a query supplied by a client. There are currently about 30 of these.



 Comments   
Comment by Githook User [ 28/Apr/20 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com'}

Message: SERVER-44689 Add serverStatus counter for each use of an aggregation stage in a user's request

(cherry picked from commit c54a777a4a154984f5595b11993d7d009350a38c)
(cherry picked from commit 08266fc2ad15e2cba4af79e58a83e822e7c540dc)
Branch: v4.0
https://github.com/mongodb/mongo/commit/3e49ba9571c3513f7aef3135b5923c83a76344e2

Comment by Githook User [ 08/Apr/20 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com'}

Message: SERVER-44689 Add serverStatus counter for each use of an aggregation stage in a user's request

(cherry picked from commit c54a777a4a154984f5595b11993d7d009350a38c)
Branch: v4.2
https://github.com/mongodb/mongo/commit/08266fc2ad15e2cba4af79e58a83e822e7c540dc

Comment by Githook User [ 08/Apr/20 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com'}

Message: SERVER-44689 Add serverStatus counter for each use of an aggregation stage in a user's request

(cherry picked from commit 13e55a2e6afc0836431051be275a8a9584eb6a32)
Branch: v4.2
https://github.com/10gen/mongo-enterprise-modules/commit/e7a577a6c1c9f8ad30679da58b2f25eca410febf

Comment by Githook User [ 19/Feb/20 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com'}

Message: SERVER-44689 Add serverStatus counter for each use of an aggregation stage in a user's request
Branch: master
https://github.com/mongodb/mongo/commit/c54a777a4a154984f5595b11993d7d009350a38c

Comment by Githook User [ 19/Feb/20 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com'}

Message: SERVER-44689 Add serverStatus counter for each use of an aggregation stage in a user's request
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/13e55a2e6afc0836431051be275a8a9584eb6a32

Comment by Bruce Lucas (Inactive) [ 19/Nov/19 ]

I think that's fine, particularly if, like commands, only a subset of them are generally very active (incrementing). Counters that don't change are inexpensive.

Comment by Andy Schwerin [ 19/Nov/19 ]

It’s somewhere between 25 and 30 counters. I had planned to send them to FTDC, but we could consider just making it available in a way that “last pings” type monitoring finds it.

Comment by Bruce Lucas (Inactive) [ 19/Nov/19 ]

How many counters do you expect that this will add? Will it be included in ftdc?

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