blocks|key|195667|text|我最终解决了这个问题，就像这样启动了mongod+(被锤击和丑陋，是的……但适用于开发环境)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|195668|mongod+--profile=1+--slowms=1+&|code-block|syntax|javascript|195669|这将启用性能分析，并将“慢查询”的阈值设置为1ms，导致所有查询都作为“慢查询”记录到文件中：|195670|/var/log/mongodb/mongodb.log|195671|现在，我使用以下命令获得连续的日志输出：|195672|tail+-f+/var/log/mongodb/mongodb.log|195673|示例日志：|195674|Mon+Mar++4+15:02:55+[conn1]+query+dendro.quads+query:+{+graph:+"u:http://example.org/people"+}+ntoreturn:0+ntoskip:0+nscanned:6+keyUpdates:0+locks(micros)+r:73163+nreturned:6+reslen:9884+88ms|195675|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

I ended up solving this by starting mongod like this (hammered and ugly, yeah... but works for development environment):

<pre><code>mongod --profile=1 --slowms=1 &amp;
</code></pre>

This enables profiling and sets the threshold for "slow queries" as 1ms, causing all queries to be logged as "slow queries" to the file:

<pre><code>/var/log/mongodb/mongodb.log
</code></pre>

Now I get continuous log outputs using the command:

<pre><code>tail -f /var/log/mongodb/mongodb.log
</code></pre>

An example log:

<pre><code>Mon Mar 4 15:02:55 [conn1] query dendro.quads query: { graph: "u:http://example.org/people" } ntoreturn:0 ntoskip:0 nscanned:6 keyUpdates:0 locks(micros) r:73163 nreturned:6 reslen:9884 88ms
</code></pre>

blocks|key|196253|text|您可以记录所有查询：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|196254|$+mongo
MongoDB+shell+version:+2.4.9
connecting+to:+test
>+use+myDb
switched+to+db+myDb
>+db.getProfilingLevel()
0
>+db.setProfilingLevel(2)
{+"was"+:+0,+"slowms"+:+1,+"ok"+:+1+}
>+db.getProfilingLevel()
2
>+db.system.profile.find().pretty()|code-block|syntax|javascript|196255|来源：http://docs.mongodb.org/manual/reference/method/db.setProfilingLevel/|offset|length|196256|db.setProfilingLevel(2)表示“记录所有操作”。|style|CODE|196257|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.mongodb.org/manual/reference/method/db.setProfilingLevel/^0|0|0|3|1X|0|0|0|N|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@$I|Z|J|10|1|11]]|A|$]]|$1|K|3|L|5|6|7|12|8|@$I|13|J|14|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

You can log all queries:

<pre><code>$ mongo
MongoDB shell version: 2.4.9
connecting to: test
&gt; use myDb
switched to db myDb
&gt; db.getProfilingLevel()
0
&gt; db.setProfilingLevel(2)
{ "was" : 0, "slowms" : 1, "ok" : 1 }
&gt; db.getProfilingLevel()
2
&gt; db.system.profile.find().pretty()
</code></pre>

Source: <a href="http://docs.mongodb.org/manual/reference/method/db.setProfilingLevel/" rel="noreferrer">http://docs.mongodb.org/manual/reference/method/db.setProfilingLevel/</a>

<code>db.setProfilingLevel(2)</code> means "log all operations".

blocks|key|2822459|text|因为它是谷歌的第一个答案…|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2822460|对于版本3|2822461|$+mongo
MongoDB+shell+version:+3.0.2
connecting+to:+test
>+use+myDb
switched+to+db
>+db.setLogLevel(1)|code-block|syntax|javascript|2822462|http://docs.mongodb.org/manual/reference/method/db.setLogLevel/|offset|length|2822463|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|1R|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|V|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|W|8|@]|9|@$K|X|L|Y|1|Z]]|A|$]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|J]]]]

Because its google first answer ...
 
For version 3

<pre><code>$ mongo
MongoDB shell version: 3.0.2
connecting to: test
&gt; use myDb
switched to db
&gt; db.setLogLevel(1)
</code></pre>

<a href="http://docs.mongodb.org/manual/reference/method/db.setLogLevel/" rel="noreferrer">http://docs.mongodb.org/manual/reference/method/db.setLogLevel/</a>

blocks|key|198315|text|MongoDB有一个复杂的分析功能。日志记录发生在system.profile集合中。可以从以下位置查看日志：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|198316|db.system.profile.find()|code-block|syntax|javascript|198317|有3个日志记录级别(source)：|198318|198319|Level+0+-探查器关闭，不收集任何数据。mongod总是将比slowOpThresholdMs阈值更长的操作写入其日志。这是默认的profiler+level.|unordered-list-item|BOLD|198320|Level+1+-仅收集运行缓慢的性能分析数据。默认情况下，慢操作是那些慢于100毫秒的操作。您可以使用slowOpThresholdMs运行时选项或setParameter命令修改“慢”操作的阈值。有关更多information.|198321|Level+2+-收集所有数据库操作的性能分析数据，请参阅指定慢速操作的阈值部分。|198322|198323|要查看数据库在哪个分析级别下运行，请使用|198324|db.getProfilingLevel()|198325|并查看状态|198326|db.getProfilingStatus()|198327|要更改性能分析状态，请使用以下命令|198328|db.setProfilingLevel(level,+milliseconds)|198329|其中level是指分析级别，milliseconds是需要记录查询持续时间的毫秒。要关闭日志记录，请使用|198330|db.setProfilingLevel(0)|198331|在系统配置文件集合中查找耗时超过一秒的所有查询(按时间戳降序排序)的查询将为|198332|db.system.profile.find(+{+millis+:+{+$gt:1000+}+}+).sort(+{+ts+:+-1+}+)|198333|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.mongodb.com/v3.2/tutorial/manage-the-database-profiler/#profiling-levels^0|0|7|P|E|0|0|A|6|0|0|0|0|7|0|0|7|0|0|7|0|0|0|0|0|0|0|0|2|5|E|C|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1O|8|@$9|1P|A|1Q|B|C]|$9|1R|A|1S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1U|8|@]|D|@$9|1V|A|1W|1|1X]]|E|$]]|$1|M|3|-4|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|1Z|8|@$9|20|A|21|B|Q]]|D|@]|E|$]]|$1|R|3|S|5|P|7|22|8|@$9|23|A|24|B|Q]]|D|@]|E|$]]|$1|T|3|U|5|P|7|25|8|@$9|26|A|27|B|Q]]|D|@]|E|$]]|$1|V|3|-4|5|6|7|28|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|29|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|H|7|2A|8|@]|D|@]|E|$I|J]]|$1|10|3|11|5|6|7|2B|8|@]|D|@]|E|$]]|$1|12|3|13|5|H|7|2C|8|@]|D|@]|E|$I|J]]|$1|14|3|15|5|6|7|2D|8|@]|D|@]|E|$]]|$1|16|3|17|5|H|7|2E|8|@]|D|@]|E|$I|J]]|$1|18|3|19|5|6|7|2F|8|@$9|2G|A|2H|B|C]|$9|2I|A|2J|B|C]]|D|@]|E|$]]|$1|1A|3|1B|5|H|7|2K|8|@]|D|@]|E|$I|J]]|$1|1C|3|1D|5|6|7|2L|8|@]|D|@]|E|$]]|$1|1E|3|1F|5|H|7|2M|8|@]|D|@]|E|$I|J]]|$1|1G|3|-4|5|6|7|2N|8|@]|D|@]|E|$]]]|1H|$1I|$5|1J|1K|1L|E|$1M|1N]]]]

<code>MongoDB</code> has a sophisticated feature of profiling. The logging happens in <code>system.profile</code> collection. The logs can be seen from: 

<pre><code>db.system.profile.find()
</code></pre>

There are 3 logging levels (<a href="https://docs.mongodb.com/v3.2/tutorial/manage-the-database-profiler/#profiling-levels" rel="noreferrer">source</a>):

<ul>
<li>Level 0 - the profiler is off, does not collect any data. mongod always writes operations longer than the slowOpThresholdMs threshold to its log. This is the default profiler level.</li>
<li>Level 1 - collects profiling data for slow operations only. By default slow operations are those slower than 100 milliseconds.
You can modify the threshold for “slow” operations with the slowOpThresholdMs runtime option or the setParameter command. See the Specify the Threshold for Slow Operations section for more information.</li>
<li>Level 2 - collects profiling data for all database operations.</li>
</ul>

To see what profiling level the database is running in, use

<pre><code>db.getProfilingLevel()
</code></pre>

and to see the status 

<pre><code>db.getProfilingStatus()
</code></pre>

To change the profiling status, use the command 

<pre><code>db.setProfilingLevel(level, milliseconds)
</code></pre>

Where <code>level</code> refers to the profiling level and <code>milliseconds</code> is the ms of which duration the queries needs to be logged. To turn off the logging, use 

<pre><code>db.setProfilingLevel(0)
</code></pre>

The query to look in the system profile collection for all queries that took longer than one second, ordered by timestamp descending will be 

<pre><code>db.system.profile.find( { millis : { $gt:1000 } } ).sort( { ts : -1 } )
</code></pre>

blocks|key|198247|text|我创建了一个命令行工具来激活分析器活动，并以一种“尾巴”方式查看日志-->+"mongotail"|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|198248|$+mongotail+MYDATABASE
2015-02-24+19:17:01.194+QUERY++[Company]+:+{"_id":+ObjectId("548b164144ae122dc430376b")}.+1+returned.
2015-02-24+19:17:01.195+QUERY++[User]+:+{"_id":+ObjectId("549048806b5d3db78cf6f654")}.+1+returned.
2015-02-24+19:17:01.196+UPDATE+[Activation]+:+{"_id":+"AB524"},+{"_id":+"AB524",+"code":+"f2cbad0c"}.+1+updated.
2015-02-24+19:17:10.729+COUNT++[User]+:+{"active":+{"$exists":+true},+"firstName":+{"$regex":+"mac"}}
...|code-block|syntax|javascript|198249|但更有趣的特性(也类似于tail)是使用-f选项“实时”查看更改，偶尔使用grep过滤结果以查找特定操作。|CODE|198250|请参阅：https://github.com/mrsarm/mongotail中的文档和安装说明|198251|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/mrsarm/mongotail^0|12|B|0|0|C|4|K|2|11|4|0|4|Z|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|10|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|11|8|@$9|12|A|13|B|M]|$9|14|A|15|B|M]|$9|16|A|17|B|M]]|D|@]|E|$]]|$1|N|3|O|5|6|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|P|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|Q|$R|$5|S|T|U|E|$V|W]]]]

I made a command line tool to activate the profiler activity and see the logs in a &quot;tail&quot;able way --&gt; &quot;mongotail&quot;:
<pre><code>$ mongotail MYDATABASE
2015-02-24 19:17:01.194 QUERY [Company] : {&quot;_id&quot;: ObjectId(&quot;548b164144ae122dc430376b&quot;)}. 1 returned.
2015-02-24 19:17:01.195 QUERY [User] : {&quot;_id&quot;: ObjectId(&quot;549048806b5d3db78cf6f654&quot;)}. 1 returned.
2015-02-24 19:17:01.196 UPDATE [Activation] : {&quot;_id&quot;: &quot;AB524&quot;}, {&quot;_id&quot;: &quot;AB524&quot;, &quot;code&quot;: &quot;f2cbad0c&quot;}. 1 updated.
2015-02-24 19:17:10.729 COUNT [User] : {&quot;active&quot;: {&quot;$exists&quot;: true}, &quot;firstName&quot;: {&quot;$regex&quot;: &quot;mac&quot;}}
...
</code></pre>
But the more interesting feature (also like <code>tail</code>) is to see the changes in &quot;real time&quot; with the <code>-f</code> option, and occasionally filter the result with <code>grep</code> to find a particular operation.
See documentation and installation instructions in: <a href="https://github.com/mrsarm/mongotail" rel="nofollow noreferrer">https://github.com/mrsarm/mongotail</a>

blocks|key|194040|text|如果您希望将查询记录到mongodb日志文件中，则必须同时设置日志级别和分析，例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|194041|db.setLogLevel(1)
db.setProfilingLevel(2)|code-block|syntax|javascript|194042|(参见https://docs.mongodb.com/manual/reference/method/db.setLogLevel)|offset|length|194043|仅设置性能分析不会将查询记录到文件中，因此只能从|194044|db.system.profile.find().pretty()|194045|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.mongodb.com/manual/reference/method/db.setLogLevel^0|0|0|3|1R|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@$I|Z|J|10|1|11]]|A|$]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

if you want the queries to be logged to mongodb log file, you have to set both 
the log level and the profiling, like for example: 

<pre><code>db.setLogLevel(1)
db.setProfilingLevel(2)
</code></pre>

(see <a href="https://docs.mongodb.com/manual/reference/method/db.setLogLevel" rel="noreferrer">https://docs.mongodb.com/manual/reference/method/db.setLogLevel</a>)

Setting only the profiling would not have the queries logged to file, so you can only get it from 

<pre><code>db.system.profile.find().pretty()
</code></pre>

blocks|key|2822483|text|一旦使用db.setProfilingLevel(2)设置了分析级别。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2822484|下面的命令将打印上次执行的查询。|2822485|您还可以更改限制(5)以查看更少/更多的查询。|2822486|$nin+-将过滤掉配置文件和索引查询|2822487|此外，使用查询投影{'+query+':1}仅用于查看查询字段|2822488|db.system.profile.find(
{+
++++ns:+{+
++++++++$nin+:+['meteor.system.profile','meteor.system.indexes']
++++}
}+
).limit(5).sort(+{+ts+:+-1+}+).pretty()|code-block|syntax|javascript|2822489|仅包含查询投影的日志|2822490|db.system.profile.find(
{+
++++ns:+{+
++++++++$nin+:+['meteor.system.profile','meteor.system.indexes']
++++}
},
{'query':1}
).limit(5).sort(+{+ts+:+-1+}+).pretty()|2822491|entityMap^0|4|N|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|13|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|14|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|15|8|@]|D|@]|E|$Q|R]]|$1|S|3|T|5|6|7|16|8|@]|D|@]|E|$]]|$1|U|3|V|5|P|7|17|8|@]|D|@]|E|$Q|R]]|$1|W|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|X|$]]

Once profiling level is set using <code>db.setProfilingLevel(2)</code>. 

The below command will print the last executed query. 
You may change the limit(5) as well to see less/more queries. 
$nin - will filter out profile and indexes queries 
Also, use the query projection {'query':1} for only viewing query field

<pre><code>db.system.profile.find(
{ 
 ns: { 
 $nin : ['meteor.system.profile','meteor.system.indexes']
 }
} 
).limit(5).sort( { ts : -1 } ).pretty()
</code></pre>

Logs with only query projection

<pre><code>db.system.profile.find(
{ 
 ns: { 
 $nin : ['meteor.system.profile','meteor.system.indexes']
 }
},
{'query':1}
).limit(5).sort( { ts : -1 } ).pretty()
</code></pre>

blocks|key|2822300|text|探查器数据将写入数据库中的集合，而不是文件。请参阅http://docs.mongodb.org/manual/tutorial/manage-the-database-profiler/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2822301|我推荐使用10gen的MMS服务，并在那里提供开发分析器数据，您可以在UI中对其进行过滤和排序。|2822302|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.mongodb.org/manual/tutorial/manage-the-database-profiler/|1|http://mms.10gen.com/^0|P|1X|0|0|B|3|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

The profiler data is written to a collection in your DB, not to file. See <a href="http://docs.mongodb.org/manual/tutorial/manage-the-database-profiler/">http://docs.mongodb.org/manual/tutorial/manage-the-database-profiler/</a>

I would recommend using 10gen's <a href="http://mms.10gen.com">MMS</a> service, and feed development profiler data there, where you can filter and sort it in the UI.

blocks|key|3034897|text|我认为虽然不是很优雅，但oplog可以部分用于此目的:它记录所有写入-但不记录读取……|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3034898|如果我是对的，你必须启用复制。该信息来自this+answer，来自以下问题：How+to+listen+for+changes+to+a+MongoDB+collection?|3034899|entityMap|0|LINK|mutability|MUTABLE|url|http://www.briancarpio.com/2012/04/21/mongodb-the-oplog-explain/|1|https://stackoverflow.com/a/9692678/1667004|2|https://stackoverflow.com/questions/9691316/how-to-listen-for-changes-to-a-mongodb-collection^0|C|5|0|0|K|B|1|13|1E|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]|$A|Z|B|10|1|11]]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

I think that while not elegant, the <a href="http://www.briancarpio.com/2012/04/21/mongodb-the-oplog-explain/" rel="nofollow noreferrer">oplog</a> could be partially used for this purpose: it logs all the writes - but not the reads... 

You have to enable replicatoon, if I'm right. The information is from <a href="https://stackoverflow.com/a/9692678/1667004">this answer</a> from this question: <a href="https://stackoverflow.com/questions/9691316/how-to-listen-for-changes-to-a-mongodb-collection">How to listen for changes to a MongoDB collection?</a>

blocks|key|196235|text|将profilinglevel设置为2是记录所有查询的另一个选项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|196236|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Setting profilinglevel to 2 is another option to log all queries.

blocks|key|2822719|text|db.setProfilingLevel(2,-1)|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2822720|这起作用了！它将所有的查询信息记录在mongod日志文件中。|unstyled|2822721|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>db.setProfilingLevel(2,-1)
</code></pre>
This worked! it logged all query info in mongod log file

blocks|key|198226|text|我推荐你去看看mongosniff。这个罐头工具可以做任何你想做的事情，甚至更多。特别是，它可以帮助诊断更大规模的mongo系统的问题，以及查询是如何路由的，以及它们来自哪里，因为它通过监听所有与mongo相关的通信的网络接口来工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|198227|http://docs.mongodb.org/v2.2/reference/mongosniff/|offset|length|198228|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1E|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

I recommend checking out mongosniff. This can tool can do everything you want and more. Especially it can help diagnose issues with larger scale mongo systems and how queries are being routed and where they are coming from since it works by listening to your network interface for all mongo related communications.

<a href="http://docs.mongodb.org/v2.2/reference/mongosniff/" rel="nofollow">http://docs.mongodb.org/v2.2/reference/mongosniff/</a>

blocks|key|2822563|text|我编写了一个脚本，该脚本将在收到查询时实时打印出system.profile日志。您需要首先启用日志记录，如其他答案中所述。我需要它，因为我正在使用Windows+Subsystem+for+Linux，它的tail仍然不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2822564|https://github.com/dtruel/mongo-live-logger|offset|length|2822565|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|17|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

I wrote a script that will print out the system.profile log in real time as queries come in. You need to enable logging first as stated in other answers. I needed this because I'm using Windows Subsystem for Linux, for which tail still doesn't work.

<a href="https://github.com/dtruel/mongo-live-logger" rel="nofollow noreferrer">https://github.com/dtruel/mongo-live-logger</a>

blocks|key|198392|text|db.adminCommand(+{+getLog:+"*"+}+)|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|198393|然后|unstyled|198394|db.adminCommand(+{+getLog+:+"global"+}+)|198395|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|L|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$B|C]]|$1|I|3|-4|5|F|7|N|8|@]|9|@]|A|$]]]|J|$]]

<pre><code>db.adminCommand( { getLog: "*" } )
</code></pre>

Then

<pre><code>db.adminCommand( { getLog : "global" } )
</code></pre>

blocks|key|2822680|text|这在很久以前就被问过了，但这仍然可能会对某些人有所帮助：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2822681|MongoDB事件探查器记录封顶集合system.profile.中的所有查询看看这个：database+profiler|offset|length|style|BOLD|2822682|2822683|使用--profile=2选项启动mongoshell实例，该选项允许记录所有查询或，如果mongoshell实例已经在运行，则在选择数据库后从mongoshell运行db.setProfilingLevel(2)。(它可以由db.getProfilingLevel()验证，它应该返回2)|ordered-list-item|CODE|2822684|After，我已经创建了一个脚本，它利用mongodb的tailable+cursor来跟踪这个system.profile集合，并将条目写到一个文件中。要查看日志，我只需要跟踪它：tail+-f+../logs/mongologs.txt。此脚本可在后台启动，它将在文件中记录对数据库的所有操作。|2822685|2822686|我的system.profile集合的tailable+cursor代码在nodejs中；它记录每个MyDb集合中发生的所有操作和查询：|2822687|const+MongoClient+=+require('mongodb').MongoClient;
const+assert+=+require('assert');
const+fs+=+require('fs');
const+file+=+'../logs/mongologs'
//+Connection+URL
const+url+=+'mongodb://localhost:27017';

//+Database+Name
const+dbName+=+'MyDb';
//Mongodb+connection

MongoClient.connect(url,+function+(err,+client)+{
+++assert.equal(null,+err);
+++const+db+=+client.db(dbName);
+++listen(db,+{})
});

function+listen(db,+conditions)+{
var+filter+=+{+ns:+{+$ne:+'MyDb.system.profile'+}+};+//filter+for+query
//e.g.+if+we+need+to+log+only+insert+queries,+use+{op:'insert'}
//e.g.+if+we+need+to+log+operation+on+only+'MyCollection'+collection,+use+{ns:+'MyDb.MyCollection'}
//we+can+give+a+lot+of+filters,+print+and+check+the+'document'+variable+below

//+set+MongoDB+cursor+options
var+cursorOptions+=+{
++++tailable:+true,
++++awaitdata:+true,
++++numberOfRetries:+-1
};

//+create+stream+and+listen
var+stream+=+db.collection('system.profile').find(filter,+cursorOptions).stream();

//+call+the+callback
stream.on('data',+function+(document)+{
++++//this+will+run+on+every+operation/query+done+on+our+database
++++//print+'document'+to+check+the+keys+based+on+which+we+can+filter
++++//delete+data+which+we+dont+need+in+our+log+file

++++delete+document.execStats;
++++delete+document.keysExamined;
++++//-----
++++//-----

++++//append+the+log+generated+in+our+log+file+which+can+be+tailed+from+command+line
++++fs.appendFile(file,+JSON.stringify(document)+%2B+'\n',+function+(err)+{
++++++++if+(err)+(console.log('err'))
++++})

});

}|code-block|syntax|javascript|2822688|对于使用pymongo的python中的tailable游标，请参考以下代码，该代码过滤MyCollection和仅插入操作：|2822689|import+pymongo
import+time
client+=+pymongo.MongoClient()
oplog+=+client.MyDb.system.profile
first+=+oplog.find().sort('$natural',+pymongo.ASCENDING).limit(-1).next()

ts+=+first['ts']
while+True:
++++cursor+=+oplog.find({'ts':+{'$gt':+ts},+'ns':+'MyDb.MyCollection',+'op':+'insert'},
++++++++++++++++++++++++cursor_type=pymongo.CursorType.TAILABLE_AWAIT)
++++while+cursor.alive:
++++++++for+doc+in+cursor:
++++++++++++ts+=+doc['ts']
++++++++++++print(doc)
++++++++++++print('\n')
++++++++time.sleep(1)|2822690|注意:+Tailable+cursor仅适用于有上限的集合。它不能直接用于记录对集合的操作，而应使用filter:+'ns':+'MyDb.MyCollection'|2822691|注意:我知道上面的nodejs和python代码可能对某些人没有多大帮助。我刚刚提供了代码以供参考。|2822692|使用此链接以您的语言/驱动程序选择Mongodb+Drivers查找可拖尾光标的文档|2822693|我在此logrotate之后添加的另一个功能。|2822694|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.mongodb.com/manual/tutorial/manage-the-database-profiler/|1|https://docs.mongodb.com/manual/core/tailable-cursors/|2|https://docs.mongodb.com/ecosystem/drivers/|3|https://linux.die.net/man/8/logrotate^0|0|I|E|18|H|0|0|0|2|B|2C|N|35|M|3Z|1|15|1|0|2J|T|S|F|1|0|0|0|0|0|0|0|1L|1M|P|1M|P|0|0|H|F|2|0|3|9|3|0^^$0|@$1|2|3|4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1N|8|@$D|1O|E|1P|F|G]]|9|@$D|1Q|E|1R|1|1S]]|A|$]]|$1|H|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1U|8|@$D|1V|E|1W|F|L]|$D|1X|E|1Y|F|L]|$D|1Z|E|20|F|L]|$D|21|E|22|F|L]|$D|23|E|24|F|G]]|9|@]|A|$]]|$1|M|3|N|5|K|7|25|8|@$D|26|E|27|F|L]]|9|@$D|28|E|29|1|2A]]|A|$]]|$1|O|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|2C|8|@]|9|@]|A|$]]|$1|R|3|S|5|T|7|2D|8|@]|9|@]|A|$U|V]]|$1|W|3|X|5|6|7|2E|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|T|7|2F|8|@]|9|@]|A|$U|V]]|$1|10|3|11|5|6|7|2G|8|@$D|2H|E|2I|F|G]|$D|2J|E|2K|F|G]|$D|2L|E|2M|F|L]]|9|@]|A|$]]|$1|12|3|13|5|6|7|2N|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|2O|8|@]|9|@$D|2P|E|2Q|1|2R]]|A|$]]|$1|16|3|17|5|6|7|2S|8|@]|9|@$D|2T|E|2U|1|2V]]|A|$]]|$1|18|3|-4|5|6|7|2W|8|@]|9|@]|A|$]]]|19|$1A|$5|1B|1C|1D|A|$1E|1F]]|1G|$5|1B|1C|1D|A|$1E|1H]]|1I|$5|1B|1C|1D|A|$1E|1J]]|1K|$5|1B|1C|1D|A|$1E|1L]]]]

This was asked a long time ago but this may still help someone:

MongoDB profiler logs all the queries in the capped collection system.profile. See this: <a href="https://docs.mongodb.com/manual/tutorial/manage-the-database-profiler/" rel="nofollow noreferrer">database profiler</a>

<ol>
<li>Start mongod instance with <code>--profile=2</code> option that enables logging all queries
OR if mongod instances is already running, from mongoshell, run <code>db.setProfilingLevel(2)</code> after selecting database. (it can be verified by <code>db.getProfilingLevel()</code>, which should return <code>2</code>)</li>
<li>After this, I have created a script which utilises mongodb's <a href="https://docs.mongodb.com/manual/core/tailable-cursors/" rel="nofollow noreferrer">tailable cursor</a> to tail this system.profile collection and write the entries in a file.
To view the logs I just need to tail it:<code>tail -f ../logs/mongologs.txt</code>.
This script can be started in background and it will log all the operation on the db in the file.</li>
</ol>

My code for tailable cursor for the system.profile collection is in nodejs; it logs all the operations along with queries happening in every collection of MyDb:

<pre><code>const MongoClient = require('mongodb').MongoClient;
const assert = require('assert');
const fs = require('fs');
const file = '../logs/mongologs'
// Connection URL
const url = 'mongodb://localhost:27017';

// Database Name
const dbName = 'MyDb';
//Mongodb connection

MongoClient.connect(url, function (err, client) {
 assert.equal(null, err);
 const db = client.db(dbName);
 listen(db, {})
});

function listen(db, conditions) {
var filter = { ns: { $ne: 'MyDb.system.profile' } }; //filter for query
//e.g. if we need to log only insert queries, use {op:'insert'}
//e.g. if we need to log operation on only 'MyCollection' collection, use {ns: 'MyDb.MyCollection'}
//we can give a lot of filters, print and check the 'document' variable below

// set MongoDB cursor options
var cursorOptions = {
 tailable: true,
 awaitdata: true,
 numberOfRetries: -1
};

// create stream and listen
var stream = db.collection('system.profile').find(filter, cursorOptions).stream();

// call the callback
stream.on('data', function (document) {
 //this will run on every operation/query done on our database
 //print 'document' to check the keys based on which we can filter
 //delete data which we dont need in our log file

 delete document.execStats;
 delete document.keysExamined;
 //-----
 //-----

 //append the log generated in our log file which can be tailed from command line
 fs.appendFile(file, JSON.stringify(document) + '\n', function (err) {
 if (err) (console.log('err'))
 })

});

}
</code></pre>

For tailable cursor in python using pymongo, refer the following code which filters for MyCollection and only insert operation:

<pre><code>import pymongo
import time
client = pymongo.MongoClient()
oplog = client.MyDb.system.profile
first = oplog.find().sort('$natural', pymongo.ASCENDING).limit(-1).next()

ts = first['ts']
while True:
 cursor = oplog.find({'ts': {'$gt': ts}, 'ns': 'MyDb.MyCollection', 'op': 'insert'},
 cursor_type=pymongo.CursorType.TAILABLE_AWAIT)
 while cursor.alive:
 for doc in cursor:
 ts = doc['ts']
 print(doc)
 print('\n')
 time.sleep(1)
</code></pre>

Note: Tailable cursor only works with capped collections. It cannot be used to log operations on a collection directly, instead use filter: <code>'ns': 'MyDb.MyCollection'</code> 

Note: I understand that the above nodejs and python code may not be of much help for some. I have just provided the codes for reference.

Use this link to find documentation for tailable cursor in your languarge/driver choice <a href="https://docs.mongodb.com/ecosystem/drivers/" rel="nofollow noreferrer">Mongodb Drivers</a>

Another feature that i have added after this <a href="https://linux.die.net/man/8/logrotate" rel="nofollow noreferrer">logrotate</a>.

blocks|key|196347|text|尝试使用这个包来跟踪所有查询(不需要oplog操作)：https://www.npmjs.com/package/mongo-tail-queries|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|196348|(免责声明:我写这个包就是为了这个需要)|196349|entityMap|0|LINK|mutability|MUTABLE|url|https://www.npmjs.com/package/mongo-tail-queries^0|R|1C|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Try out this package to tail all the queries (without oplog operations): <a href="https://www.npmjs.com/package/mongo-tail-queries" rel="nofollow noreferrer">https://www.npmjs.com/package/mongo-tail-queries</a>

(Disclaimer: I wrote this package exactly for this need)

The question is as basic as it is simple... How do you log all queries in a "tail"able log file in mongodb?

I have tried:

<ul>
<li>setting the profiling level </li>
<li>setting the slow ms parameter starting</li>
<li>mongod with the -vv option</li>
</ul>

The /var/log/mongodb/mongodb.log keeps showing just the current number of active connections...

MongoDB logging all queries

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

这个问题既简单又基本……在mongodb中，如何将所有查询记录在一个“结尾”的日志文件中？我试过了：设置性能分析级别使用-vv选项设置慢毫秒参数/var/log/mongodb/mongodb.log只显示当前活动连接的数量……

问MongoDB记录所有查询
EN

回答 16

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MongoDB记录所有查询EN

回答 16

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MongoDB记录所有查询
EN