[DOCS-8121] 3.4 CRUD diagnostics change Created: 17/Jun/16  Updated: 06/Dec/22  Resolved: 11/Nov/16

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

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Steve Renaker (Inactive)
Resolution: Done Votes: 0
Labels: docs-3.4
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
Participants:
Days since reply: 7 years, 13 weeks ago
Story Points: 2

 Description   

See the linked PM ticket for scope/spec



 Comments   
Comment by Githook User [ 17/Nov/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-8121: fix include
Branch: master
https://github.com/mongodb/docs/commit/608b5a7bdc969491be947c4ed0836d14123a009f

Comment by Githook User [ 11/Nov/16 ]

Author:

{u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}

Message: DOCS-8121: 3.4 CRUD diagnostics change

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/0da99365e9c42469ec294b4892dac878994072d7

Comment by Ravind Kumar (Inactive) [ 16/Sep/16 ]

Yeah, we have this page on the profiler. I'll update both with the same general information.

Comment by David Storch [ 16/Sep/16 ]

ravind.kumar that sounds good. You may also have to make some updates to the db.currentOp() page: https://docs.mongodb.com/manual/reference/method/db.currentOp/. Do we have similar detailed documentation describing the diagnostic info reported in system.profile?

Comment by Ravind Kumar (Inactive) [ 16/Sep/16 ]

david.storch, same question with this one as DOCS-8120, this feels like it would fall under release notes, with maybe a note in the database profile page noting that MongoDB 3.4 diagnostic data is uniform across the profiler, log, and currentOp() for the commands listed in the spec doc. Does that sound about right?

Generated at Thu Feb 08 07:55:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.