[SERVER-28304] Profiler level 2 should not filter on sample rate Created: 14/Mar/17  Updated: 06/Dec/17  Resolved: 06/Apr/17

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: 3.5.4
Fix Version/s: 3.5.6

Type: Improvement Priority: Major - P3
Reporter: James Wahlin Assignee: Nicholas Zolnierz
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Query 2017-04-17
Participants:

 Description   

The ability to filter profiler and log writes by a sample rate was added under SERVER-4786 for MongoDB 3.6. As currently implemented, this filter applies to all profiler levels, including level 2 which historically could be counted on to write a profiler entry for every operation (regardless of slowms setting). We should consider limiting the sample rate to profiler levels 0 and 1 which will bring it inline with how slowms works.



 Comments   
Comment by Githook User [ 06/Apr/17 ]

Author:

{u'username': u'nzolnierzmdb', u'name': u'Nick Zolnierz', u'email': u'nicholas.zolnierz@mongodb.com'}

Message: SERVER-28304 Profiler level 2 should not filter on sample rate
Branch: master
https://github.com/mongodb/mongo/commit/2f1c0cfb1704caa14e8fec482ee5bcd16081cfed

Generated at Thu Feb 08 04:17:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.