[SERVER-1772] getProfilingLevel() should include slowms Created: 10/Sep/10  Updated: 12/Jul/16  Resolved: 13/Sep/10

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

Type: Improvement Priority: Minor - P4
Reporter: Fitz Agard Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Running getProfilingLevel doesn't include the current slowms configuration. However, if one runs db.runCommand(

{profile:-1}

) then the slowms is returned.



 Comments   
Comment by auto [ 13/Sep/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: getProfilingStatus to replace getProfilingLevel
doc -1 gets current value
SERVER-1772
http://github.com/mongodb/mongo/commit/77955627fac376c72012e1700e4e7df51c108fc2

Comment by Eliot Horowitz (Inactive) [ 13/Sep/10 ]

added this

> db.getProfilingStatus()

{ "was" : 1, "slowms" : 100 }
Comment by Scott Hernandez (Inactive) [ 10/Sep/10 ]

"-1" should be doc'd as the value to use to get the current settings; this is what the shell does for getProfilingLevel().

Generated at Thu Feb 08 02:57:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.