[SERVER-55784] Time-series Feature Usage Metrics Created: 25/Mar/21  Updated: 29/Oct/23  Resolved: 26/May/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0-rc1, 5.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Connie Chen Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: post-rc0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Documented
is documented by DOCS-14505 Investigate changes in SERVER-55784: ... Closed
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0, v4.4
Sprint: Execution Team 2021-05-17, Execution Team 2021-05-31
Participants:
Linked BF Score: 149

 Description   

Summary

Define and add new metrics to serverStatus in order to better track collection usage via collection counts. 

Motivation

In order to make more informed product decisions and better support customers feature requests we need to have better insight into our customer usage and behavior. By adding metrics to track usage and behavior ASAP we will be able to not only measure the success of features and inits, but better understand how to develop and prioritize new features related to collection types. 



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Natalya Furmanova [ 20/Jul/21 ]

louis.williams  I'm starting to do reporting and analytics using these new outputs. Could you please confirm the following: 

What is the exact format of the subdocument? Is it the same as in the example output below (top level inside serverStatus)? 

{
"collectionStats": {
"types":

Unknown macro: { "timeseries"}

}
}

 

2) Has this been backported to version 4.4? 

3) Are there any M10 or higher tier clusters in Atlas that were used in testing this new feature? 

The reason I'm asking this is because I have not yet found these new fields in our analytical tables , but we only store M10 and higher tiers data.  [fyi michael.gargiulo ]

Comment by Githook User [ 26/May/21 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-55784 Add catalog statistics to serverStatus

Adds collection and view catalog counters to a new 'catalogStats' serverStatus section

(cherry picked from commit 2157b103fc2848ae8bf94e9450b752b6d1547863)
Branch: v5.0
https://github.com/mongodb/mongo/commit/5437aaf0e173e88a03db83560d992f6ff2c6339f

Comment by Githook User [ 26/May/21 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-55784 Add catalog statistics to serverStatus

Adds collection and view catalog counters to a new 'catalogStats' serverStatus section
Branch: master
https://github.com/mongodb/mongo/commit/2157b103fc2848ae8bf94e9450b752b6d1547863

Comment by Bruce Lucas (Inactive) [ 07/May/21 ]

Can you please update the description to summarize the proposed new metrics for serverStatus? We need to check to make sure they will be acceptable in FTDC, and whether they will be in a form useful for downstream tools.

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