Monitoring for MongoDBMongoDB监控

Free Monitoring免费监控

MongoDB offers free Cloud monitoring for standalones or replica sets.MongoDB为单机或副本集提供免费的云监控。

By default, you can enable/disable free monitoring during runtime using db.enableFreeMonitoring() and db.disableFreeMonitoring().默认情况下，您可以在运行时使用db.enableFreeMonitoring()和db.disableFreeMonitoring()启用/禁用免费监控。

Free monitoring provides up to 24 hours of data. 免费监控可提供长达24小时的数据。For more details, see Free Monitoring.有关更多详细信息，请参阅免费监控。

Utilities实用工具

The MongoDB distribution includes a number of utilities that quickly return statistics about instances' performance and activity. MongoDB发行版包括许多实用程序，它们可以快速返回有关实例性能和活动的统计信息。Typically, these are most useful for diagnosing issues and assessing normal operation.通常，这些对于诊断问题和评估正常操作最有用。

Commands命令

MongoDB includes a number of commands that report on the state of the database.MongoDB包含许多报告数据库状态的命令。

These data may provide a finer level of granularity than the utilities discussed above. 这些数据可以提供比上述实用程序更精细的粒度级别。Consider using their output in scripts and programs to develop custom alerts, or to modify the behavior of your application in response to the activity of your instance. 考虑在脚本和程序中使用它们的输出来开发自定义警报，或者修改应用程序的行为以响应实例的活动。The db.currentOp() method is another useful tool for identifying the database instance's in-progress operations.db.currentOp()方法是另一个用于识别数据库实例正在进行的操作的有用工具。

Hosted (SaaS) Monitoring Tools托管（SaaS）监控工具

These are monitoring tools provided as a hosted service, usually through a paid subscription.这些是作为托管服务提供的监控工具，通常通过付费订阅提供。

Name名称	Notes备注
MongoDB Cloud Manager	MongoDB Cloud Manager is a cloud-based suite of services for managing MongoDB deployments. MongoDB Cloud Manager是一套基于云的服务，用于管理MongoDB部署。MongoDB Cloud Manager provides monitoring, backup, and automation functionality. MongoDB Cloud Manager提供监控、备份和自动化功能。For an on-premise solution, see also Ops Manager, available in MongoDB Enterprise Advanced.有关内部部署解决方案，请参阅Ops Manager，可在MongoDB Enterprise Advanced中获得。
VividCortex	VividCortex provides deep insights into MongoDB production database workload and query performance -- in one-second resolution. VividCortex提供了对MongoDB生产数据库工作负载和查询性能的深入了解——只需一秒钟的解决方案。Track latency, throughput, errors, and more to ensure scalability and exceptional performance of your application on MongoDB.跟踪延迟、吞吐量、错误等，以确保应用程序在MongoDB上的可扩展性和卓越性能。
Scout	Several plugins, including MongoDB Monitoring, MongoDB Slow Queries, and MongoDB Replica Set Monitoring.几个插件，包括MongoDB监控、MongoDB慢速查询和MongoDB副本集监控。
Server Density服务器密度	Dashboard for MongoDBMongoDB面板, MongoDB specific alerts, replication failover timeline and iPhone, iPad and Android mobile apps.，MongoDB特定警报、复制故障转移时间表以及iPhone、iPad和Android移动应用程序。
Application Performance Management应用程序性能管理	IBM has an Application Performance Management SaaS offering that includes monitor for MongoDB and other applications and middleware.IBM有一个应用程序性能管理SaaS产品，其中包括MongoDB和其他应用程序和中间件的监视器。
New Relic	New Relic offers full support for application performance management. New Relic为应用程序性能管理提供全面支持。In addition, New Relic Plugins and Insights enable you to view monitoring metrics from Cloud Manager in New Relic.此外，New Relic插件和Insights使您能够在New Relic中查看来自Cloud Manager的监控指标。
Datadog	Infrastructure monitoring to visualize the performance of your MongoDB deployments.基础设施监控，以可视化MongoDB部署的性能。
SPM Performance MonitoringSPM性能监控	Monitoring, Anomaly Detection and Alerting监控、异常检测和警报 SPM monitors all key MongoDB metrics together with infrastructure incl. SPM监控所有关键的MongoDB指标以及基础设施，包括。Docker and other application metrics, e.g. Node.js, Java, NGINX, Apache, HAProxy or Elasticsearch. SPM provides correlation of metrics and logs.Docker和其他应用程序度量，例如Node.js、Java、NGINX、Apache、HAProxy或Elasticsearch。SPM提供度量和日志的相关性。
Pandora FMS	Pandora FMS provides the PandoraFMS-mongodb-monitoring plugin to monitor MongoDB.PandoraFMS提供PandoraFMmongodb监控插件来监控mongodb。

Log Redaction日志修改

Available in MongoDB Enterprise only仅在MongoDB Enterprise中可用

A mongod or mongos running with redactClientLogData redacts any message accompanying a given log event before logging, leaving only metadata, source files, or line numbers related to the event. 使用redactClientLogData运行的mongod或mongos会在日志记录之前对给定日志事件附带的任何消息进行编辑，只留下与该事件相关的元数据、源文件或行号。redactClientLogData prevents potentially sensitive information from entering the system log at the cost of diagnostic detail.防止潜在的敏感信息以牺牲诊断细节为代价进入系统日志。

For example, the following operation inserts a document into a mongod running without log redaction. 例如，下面的操作将一个文档插入到一个没有日志密文的mongod中。The mongod has the log verbosity level set to 1:mongod的日志详细级别设置为1：

db.clients.insertOne( { "name" : "Joe", "PII" : "Sensitive Information" } )

This operation produces the following log event:此操作将生成以下日志事件：

2017-06-09T13:35:23.446-04:00 I COMMAND  [conn1] command internal.clients
   appName: "MongoDB Shell"
   command: insert {
      insert: "clients",
      documents: [ {
            _id: ObjectId('593adc5b99001b7d119d0c97'),
            name: "Joe",
            PII: " Sensitive Information"
         } ],
      ordered: true
   }
   ...

When mongod runs with redactClientLogData and performs the same insert operation, it produces the following log event:当mongod使用redactClientLogData运行并执行相同的插入操作时，它会生成以下日志事件：

2017-06-09T13:45:18.599-04:00 I COMMAND  [conn1] command internal.clients
   appName: "MongoDB Shell"
   command: insert {
      insert: "###", documents: [ {
         _id: "###", name: "###", PII: "###"
      } ],
      ordered: "###"
   }

Use redactClientLogData in conjunction with Encryption at Rest and TLS/SSL (Transport Encryption) to assist compliance with regulatory requirements.将redactClientLogData与静态加密和TLS/SSL（传输加密）结合使用，以帮助遵守法规要求。

Flow Control流量控制

Starting in MongoDB 4.2, administrators can limit the rate at which the primary applies its writes with the goal of keeping the majority committed lag under a configurable maximum value flowControlTargetLagSeconds.从MongoDB 4.2开始，管理员可以限制主应用写入的速率，目的是将大多数提交的延迟保持在可配置的最大值flowControlTargetLagSeconds之下。

By default, flow control is enabled.默认情况下，流量控制处于启用状态。

See also: Check the Replication Lag.另请参阅：检查复制滞后。

Replica Set Status复制副本集状态

Replication issues are most often the result of network connectivity issues between members, or the result of a primary that does not have the resources to support application and replication traffic. 复制问题通常是由于成员之间的网络连接问题造成的，或者是由于primary没有资源支持应用程序和复制流量造成的。To check the status of a replica, use the replSetGetStatus or the following helper in the shell:要检查复制副本的状态，请在shell中使用replSetGetStatus或以下帮助程序：

rs.status()

The replSetGetStatus reference provides a more in-depth overview view of this output. replSetGetStatus引用提供了此输出的更深入的概述视图。In general, watch the value of optimeDate, and pay particular attention to the time difference between the primary and the secondary members.通常，请注意optimeDate的值，并特别注意primary和secondary成员之间的时间差。

Free Monitoring免费监控

Slow Application of Oplog EntriesOplog条目应用缓慢

Starting in version 4.2, secondary members of a replica set now log oplog entries that take longer than the slow operation threshold to apply. 从4.2版开始，副本集的辅助成员现在会记录应用时间超过慢速操作阈值的oplog条目。These slow oplog messages:这些慢速操作日志消息：

• Are logged for the secondaries in the diagnostic log.在诊断日志中为辅助设备记录。
• Are logged under the REPL component with the text applied op: <oplog entry> took <num>ms.在REPL组件下记录，并应用文本applied op: <oplog entry> took <num>ms。
• Do not depend on the log levels (either at the system or component level)不依赖于日志级别（在系统或组件级别）
• Do not depend on the profiling level.不要依赖于分析级别。
• May be affected by slowOpSampleRate, depending on your MongoDB version:可能会受到slowOpSampleRate的影响，具体取决于您的MongoDB版本：
  • In MongoDB 4.2, these slow oplog entries are not affected by the slowOpSampleRate. 在MongoDB 4.2中，这些慢速操作日志条目不受slowOpSampleRate的影响。MongoDB logs all slow oplog entries regardless of the sample rate.MongoDB记录所有慢速操作日志条目，而不管采样率如何。
  • In MongoDB 4.4 and later, these slow oplog entries are affected by the slowOpSampleRate.在MongoDB 4.4及更高版本中，这些慢速操作日志条目受到slowOpSampleRate的影响。

The profiler does not capture slow oplog entries.探查器未捕获慢速操作日志项。

Config Servers配置服务器

The config database maintains a map identifying which documents are on which shards. config数据库维护一个映射，用于标识哪些文档位于哪些分片上。The cluster updates this map as chunks move between shards. 当区块在分片之间移动时，集群会更新此映射。When a configuration server becomes inaccessible, certain sharding operations become unavailable, such as moving chunks and starting mongos instances. 当配置服务器变得不可访问时，某些分片操作将变得不可用，例如移动块和启动mongos实例。However, clusters remain accessible from already-running mongos instances.然而，集群仍然可以从已经运行的mongos实例访问。

Because inaccessible configuration servers can seriously impact the availability of a sharded cluster, you should monitor your configuration servers to ensure that the cluster remains well balanced and that mongos instances can restart.由于无法访问的配置服务器会严重影响分片集群的可用性，因此您应该监控配置服务器，以确保集群保持良好的平衡，并且mongos实例可以重新启动。

MongoDB Cloud Manager and Ops Manager monitor config servers and can create notifications if a config server becomes inaccessible. MongoDB Cloud Manager和Ops Manager监控配置服务器，如果配置服务器无法访问，则可以创建通知。See the MongoDB Cloud Manager documentation and Ops Manager documentation for more information.有关更多信息，请参阅MongoDB Cloud Manager文档和Ops Manager文档。

Balancing and Chunk Distribution平衡和区块分配

The most effective sharded cluster deployments evenly balance chunks among the shards. 最有效的分片集群部署在分片之间均匀地平衡块。To facilitate this, MongoDB has a background balancer process that distributes data to ensure that chunks are always optimally distributed among the shards.为了便于实现这一点，MongoDB有一个后台均衡器进程来分发数据，以确保区块始终以最佳方式分布在分片之间。

Issue the db.printShardingStatus() or sh.status() command to the mongos from within mongosh. 从mongosh中向mongos发出db.printShardingStatus()或sh.status()命令。This returns an overview of the entire cluster including the database name, and a list of the chunks.这将返回整个集群的概述，包括数据库名称和块的列表。

Stale LocksStale Locks

To check the lock status of the database, connect to a mongos instance using mongosh. 要检查数据库的锁定状态，请使用mongosh连接到mongos实例。Issue the following command sequence to switch to the config database and display all outstanding locks on the shard database:发出以下命令序列切换到config数据库，并显示分片数据库上所有未完成的锁：

use config
db.locks.find()

The balancing process takes a special "balancer" lock that prevents other balancing activity from transpiring. 平衡过程需要一个特殊的“平衡器”锁，以防止其他平衡活动发生。In the config database, use the following command to view the "balancer" lock.在config数据库中，使用以下命令查看“平衡器”锁。

db.locks.find( { _id : "balancer" } )