PCB MongoDB Monitoring

A database monitoring tool is essential and of course MongoDB is installed with self-monitoring.

The monitoring tool Mongostat.exe and Mongotop.exe use and parameters are explained here.

A. Description of the Monitoring tool:

Two. Monitoring tool enabled

1. Make a MongoDB installation directory:

CD D:\Program files\mongodb\server\4.0\ Bin

2. Start Mongostat 1 1 for monitoring time interval of 1 seconds (default is 1 seconds)

Mongostat 1

For monitoring intervals of 10 seconds

Three. Mongostat Monitoring parameter Description:

Monitoring of additions and deletions, data volume, number of connections and other information

Parameter description:

Number of inserts/queries/updates/deletions per second, Insert/query/update/delete

Getmore, number of executions per second getmore;

Number of command-and instance execution commands per second;

dirtyto generate dirty data and its size;

used, the size of the instance space being used;

The number of Fsync data writes performed per second, flushes;

vsize, virtual memory usage, Unit is g;

Res, physical memory usage, in megabytes;

QR|QW----when MongoDB receives too many commands and the database is locked cannot be completed, it joins the command to the queue. This column shows the length of the total, read, and write 3 queues, all of which are 0 words MONGO no pressure. When high concurrency occurs, the general queue value is raised.

Ar|aw, the number of connected clients that are currently active, the higher the value, the more blocking the performance of MongoDB.

netin/netout-> Network bandwidth pressure value, in general MongoDB, the network will not become a bottleneck.

Conn, current number of connections

four. Mongotop Monitoring parameter Description:

focus on monitoring is the reading and writing of instances and aggregate statistics information

Parameter description:

NS, database namespace, name, and collection;

Total time spent working on the current namespace;

time speed of read data for the current namespace;

The amount of time to write data to the current namespace, write

Five. Summary

Monitoring fine-grained:

At present MongoDB monitoring only to the database running state monitoring, unable to control which machine or user executes no SQL statement;

Compared with Microsoft's product SQL Server profile, MongoDB monitoring does have a progress space.

No graphical interface for monitoring:

No way people's tools are so old-fashioned, if not accustomed to cmd monitoring can only be self-modification, this monitoring is to the console output information,

You can redirect information from the console output to go to Web monitoring so the display is better.

PCB MongoDB Monitoring