[SERVER-19791] Save mongo shell session into a file (gdb style) Created: 06/Aug/15  Updated: 19/Jul/18  Resolved: 19/Jul/18

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

Type: New Feature Priority: Major - P3
Reporter: Dmitry Ryabtsev Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-5447 Option to write shell commands and re... Closed
Related
related to SERVER-19710 shellPrintHelper() and shellPrint() p... Closed
related to SERVER-18643 Output redirection from mongo shell Closed
related to SERVER-14880 Ability to output to file from mongo ... Backlog
Participants:

 Description   

I believe lots of people including Support team could benefit from this.

Can we implement shell session logging into a file in a fashion similar to what we have in gdb, for example (" set logging file <file_name>" & "set logging on")?



 Comments   
Comment by Ramon Fernandez Marina [ 19/Jul/18 ]

I'm going to close this as a duplicate of SERVER-5447, which is now part of an epic and therefore has a higher chance of getting scheduler sooner.

Comment by Dmitry Ryabtsev [ 09/Aug/16 ]

Ramon, I'm ok with closing this one as duplicate as long as it is clear that implementing this feature would do a great help to many TSEs out there, not only to students attending MongoDB training.

Comment by Lorne Schachter [ 09/Aug/16 ]

Ramon,

I'm fine with that if it helps movie the process along.

Thanks,
Lorne

Comment by Ramon Fernandez Marina [ 09/Aug/16 ]

I think the functionality requested in this ticket is the same one for SERVER-5447, so I propose we close this ticket as a duplicate – lorne.schachter, dmitry.ryabtsev, are you cool with that?

Comment by Lorne Schachter [ 09/Aug/16 ]

What I would be looking for is something like the 'spool' command in Oracle Sql*Plus

Comment by Lorne Schachter [ 09/Aug/16 ]

We ask clients to run commands and send us the output all the time. If we could make the process easier, by just having them direct the output to a file and attaching the file to the ticket, it would make the process more user-friendly and efficient.

Comment by Kevin Pulo [ 06/Aug/15 ]

Note that this is not just saving the shell history, which we already do (and have done for ages). This is about logging all interactive shell input and output to a file, without having to resort to mucking around with .js files, --eval, redirects, etc.

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