MongoDB Monitoring Item details (MMS)

Tag:mongodb    monitor    

The MONGODB MMS monitoring item opcounters:     currently has an operation to execute the command (Command,query,update,delete,gemore, Insert) Number of connections :      currently active connections to this server. Each connection is assigned a stack, so a very high number of connections can cause severe RAM usage page_faults :        Average rate of error on page This process memory :            resides per second during the selected sample, virtual, Size of mapped memory network :           network traffic egress and ingress traffic Db storage  :       db size scan and order:     You cannot use an index to perform an operation document metrics:    returned: Average interest rate per second query returns the document in the selected sample                                               inserted: The average speed of the document is inserted into the selected sample segment per second                                                  updated: The average rate of files updated during the selected sample. Deleted: The average rate of files deleted during the selected sample period queues                        Current Queue query executor               scanned: Average interest rate per second selected sample Segment index item scan query and query plan evaluation                               scanned objects:  average interest rate per second selected sample segment file scan in query and query plan evaluation tickets  available           read: Represents the number of parallel read operations allowed into the storage engine. When this value reaches 0, the new read request queue until the ticket is available             &NBsp;                Write: Concurrent write operations representing a number allow access to the storage engine. When this value reaches 0, the new write request queue until the ticket is available      Query Targeting              scanned / returned: The ratio of the number of indexed items to the number of documents returned by the query, because the previous data point is the selected sample period. A value of 1.0 means that all returned documents fully conform to the query criteria of the sample cycle                              scanned objects  / returned: The ratio of the number of documents scanned for the number of documents returned by the query, since the previous data point is the selected sample period cursors                       Current number of cursors replication  oplog window     approximate number of hours available Oplog primary replication. If a level two real-time exceeds this number and cannot be caught later, a full resynchronization is required asserts                       Maintenance window Cache activity               Readinto: The average rate of bytes read per second in the selected sample period is Wiredtiger cache                               Writtenfrom: In the selected sample period, the average rate of bytes written per second is Wiredtiger cache operation execution times    in the selected sample cycle, Average execution time per read/write/command operation oplog gb/hour                oplog main generated average speed per hour cache usage                  dirty: The number of dirty bytes currently being traced Wiredtiger cache                               used: Current number of bytes cached in Wiredtiger

These are the explanations given to MongoDB's official surveillance (MMS), all by self-understanding

This article is from the "Wang Xiao Acid" blog, please be sure to keep this source http://wangaimin.blog.51cto.com/8499946/1959834

MongoDB Monitoring Item details (MMS)