[SERVER-39851] Create traffic capture output in subdirectory of dbpath Created: 26/Feb/19 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Networking, Shell |
| Affects Version/s: | None |
| Fix Version/s: | features we're not sure of |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | move-stm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Tooling & Methods
|
||||||||
| Sprint: | Service Arch 2019-03-11, Service Arch 2019-03-25 | ||||||||
| Participants: | |||||||||
| Description |
|
The TrafficRecorder attempts to use logpath by default. There are two unfortunate side effects of this:
I would like us to follow the ftdc pardigm wherein by default we make a subfolder in dbpath and put files there. This has the added advantage of automatically capturing traffic recordings via resmoke rules where applicable. |
| Comments |
| Comment by Mira Carey [ 01/Apr/19 ] |
That's trafficRecordingDirectory. It's a mandatory startup param if you don't have always record traffic on
I'm pretty sure the sane thing to do here is to set trafficRecordingDirectory if we actually want to always record traffic. No need to have it piggy back on other file types. I'm going to leave this as wont fix for now, until we hook this up with a wider use of the feature |
| Comment by Benjamin Caimano (Inactive) [ 04/Mar/19 ] |
|
Ahhh, I hadn't internalized that we didn't have a true dbpath for mongos. (I walked over to Drew for more context. I miiiiiight file a ticket about formalizing server proc working directories.) So two things that occur to me here:
|
| Comment by Mira Carey [ 26/Feb/19 ] |
|
That writing to logpath is only true if ShouldAlwaysRecordTraffic is on, which is a test only thing. I buy that we could do something smarter for that, but note that traffic recording also works in mongos, that doesn't have a dbpath. I think it's also a little less risky to slam some random, start up param named file, in logpath than under dbpath (if we have to pick a directory based on existing args). |