[SERVER-5315] Add a dtrace provider for mongodb Created: 14/Mar/12  Updated: 23/Feb/23  Resolved: 24/Feb/22

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: None
Fix Version/s: features we're not sure of

Type: Improvement Priority: Minor - P4
Reporter: Jared Rosoff Assignee: Backlog - Service Architecture
Resolution: Won't Do Votes: 4
Labels: devtools-to-servicearch, re-triaged-ticket
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File mongocmd.d     File mongocmdlatency.d     File mongocmdslow.d     File mongocmdslow2.d    
Issue Links:
Related
Assigned Teams:
Service Arch
Participants:

 Description   

It would be great if we could trace mongodb using dtrace. We can do this now using the PID provider, but you need to use mangled names to trace execution. If we added the dtrace hooks, we could make it really easy to use dtrace to look at what's happening in the db kernel. I attached some simple dtrace scripts that use the mangled names to look at things like slow queries.



 Comments   
Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ]

We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Generated at Thu Feb 08 03:08:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.