disable logging of full update command

[ScottBessler]

Is there any way to disable the full update logging to --logpath?

[Eliot Horowitz]

What do you mean full update logging?

On Wed, Jan 25, 2012 at 10:49 PM, ScottBessler <scottb...@gmail.com> wrote:
> Is there any way to disable the full update logging to --logpath?
>

> --
> You received this message because you are subscribed to the Google Groups "mongodb-user" group.
> To post to this group, send email to mongod...@googlegroups.com.
> To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.
>

[ScottBessler]

It seems that when an update takes >100ms it outputs the full update
statement including the full contents of an admittedly too large
document. I was hoping to not log slow queries in the stdout/logpath
log since I can log those with the profiler if need be.

[Scott Hernandez]

You can increase the threshold (def. 100ms) but no, there is no way to
disable it all out. You can just set it to 5000 for example.

See the slowms option for mongod or settable via
db.setProfilingLevel(1, --slowms--).

[ScottBessler]

So the slowms not only controls what goes into db.profile when you
have profilingLevel(1) but also controls which queries go to the
stdout/logpath regardless of the profilingLevel?

[Scott Hernandez]

Yes, basically.