Monitoring
- Print
- PDF
Monitoring
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Available in VPC
Monitoring supports five types of dashboards, enabling you to check various monitoring information for the performance and history of MongoDB. Monitoring is a service included in NAVER Cloud Platform's Cloud DB for MongoDB, so it can be used without additional charges. The types of dashboards provided by Monitoring are as follows:
- DB Dashboard: monitoring information related to the MongoDB Server in operation
- OS Dashboard: Monitoring information related to the operating system of the MongoDB Server in operation
- DB Logs: records of occurrence time and content of all logs that occur from the MongoDB Server in operation
- Query Timeline: query execution history of the MongoDB Server in operation
- Audit: records of occurrence time and content of Audit logs that occur from the MongoDB Server in operation
You can check the performance information of the MongoDB Server within the last one year based on average values, and logs and queries from the last 4 weeks through these five types of dashboards. Each dashboard is configured with various graphic charts. You can utilize these charts in your business by printing specific graphic charts or downloading them to your local PC as files using various extensions.
Note
You can set the user to be notified when monitoring results show that a certain indicator has exceeded its threshold or met specific conditions by having them recognized as events. For more information on the detailed usage for event and notification settings, see Event.
Since the intuitive search and management for the MongoDB performance information is available without additional charges, if you wish to operate servers stably in an environment without a professional database manager, then we recommend utilizing the monitoring indicators provided through the dashboard.
Monitoring page
The basics of using Monitoring are as follows:
| Area | Description |
|---|---|
| ① Menu name | Name of the menu currently being viewed |
| ② Basic features | Cloud DB for MongoDB details confirmation, Monitoring page refresh |
| ③ MongoDB Service list | The list of the MongoDB Services in operation and the list of MongoDB Servers by service |
| ④ Dashboard | DB Dashboard, OS Dashboard, DB Logs, Query Timeline, and Audit of the selected server from the MongoDB Server list, |
View Monitoring dashboards
Dashboards provided by Monitoring consist of multiple graphic charts. You can display and intuitively check only the information you need from the dashboard of each server. The information shown in the dashboard is collected every minute to be displayed, but it shows only the average values. To use dashboards, follow these steps:
In the VPC environment of NAVER Cloud Platform console, click Services > Database > Cloud DB for MongoDB in order.
Click Monitoring menu.
Click the MongoDB Server to be monitored from the list of MongoDB Service.
Click the button for the dashboard you want to check from the page on the right.
Click and select all graphic charts you want to display and check on the dashboard.
From the period or view time selection box, click and select the period you want to view, or enter it directly.
Check the results from the dashboard.
- To see the precise indicator value of a specific point on the graphic chart: mouse over to the specific point on the graphic chart
- To see the detailed graph: double-click the graphic chart
- Print graphic chart: click
, followed by Print chart - Download a graphic chart to your local PC as a file: click , followed by the file extension menu for the file you want to download
- Download PNG image: image file with the .png extension
- Download JPEG image: image file with the .jpeg extension
- Download PDF document: document file with the .pdf extension
- Download SVG vector image: vector image file with the .svg extension
- Download CSV: document file with the .csv extension
, followed by Print chartCaution
- In step 5, the default value is select all, and in step 6, the default is the last 1 hour.
- In step 6, the period can be selected up to one year for DB Dashboard or OS Dashboard, and up to 4 weeks for DB Logs or Query Timeline.
Note
From Services > Database > Cloud DB for MongoDB > DB server, click and select the server you want, and then click [Monitoring] to go directly to the page in step 4.
DB Dashboard graphic charts
The following are some descriptions for the graphic charts configured in DB Dashboard:
| Graphic chart | Unit | Description |
|---|---|---|
| Connections | count | Number of maximum DB access sessions available, number of current access sessions, number of active sessions |
| Opcounters | count / sec | Number of executions per second by query type |
| PageFault | count | Number of reads that was read again from not being in the buffer |
| Global Lock | avg activity/sec | Global level lock |
| Database Lock | seconds | Database level lock |
| Collection Lock | total / min | Collection level lock |
| TcmallocSpinLockWait | ns | Waiting time in central heap of tcmalloc |
| WiredTiger Cache | GB | Cache information of the wiredTiger storage engine |
| WiredTiger Eviction | GB | Eviction information of the wiredTiger storage engine |
| WiredTiger Cache Ratio | % | Cache usage of the wiredTiger storage engine |
| Task Executor Pool | count | Connection pool between mongos and shard member |
| Document Metrics | count/sec | Number of documents updated/returned/deleted/inserted |
| Query Executor | count/sec | Metrics to measure index utilization |
| Concurrent Read Ticket | count | The number of concurrent read transactions (read tickets) in use or available |
| Concurrent Write Ticket | count | The number of concurrent write transactions (write tickets) in use or available |
| Replication Delay | seconds | Replication latency time (rs.printSecondaryReplicationInfo) |
| Oplog | hour | Oplog window, the value obtained by subtracting the oldest time from the most recent time in the oplog |
| MongoDB Ping | - | In MongoDB, when the result of the Ping command is 1, it means the database is in a normal and accessible state. |
| Transactions | count/sec | The number of transactions opened, transactions started, committed transactions, and aborted transactions. |
OS Dashboard graphic charts
The following are some descriptions for the graphic charts configured in OS Dashboard:
| Graphic chart | Unit | Description |
|---|---|---|
| CPU Usage | used(%) | CPU usage |
| Load Average | - | Server load |
| Memory Usage | used(%) | Memory usage |
| Swap | used(%) | Swap memory volume |
| Disk Used | GB | Disk usage |
| Disk I/O | MB / sec | Disk Input/Output volume per second |
| Network I/O | MB / sec | Network Input/Output volume per second |
DB Logs graphic charts
The following are the descriptions for the graphic charts configured in DB Logs:
| Field | Description |
|---|---|
| Time when event occurred | Time when DB Log occurred |
| Log content | DB Log content |
Note
In DB Logs, you can check the Slow Query log, Login log, Entire log of the MongoDB Server in operation.
Query Timeline graphic charts
The following are the descriptions for the graphic charts configured in the Query Timeline.
| Field | Description |
|---|---|
| Time when event occurred | Time when the query occurred |
| Log content | Content of the executed query |
Audit graphic chart
The Audit feature is provided by the Enterprise Edition product.
The Community Edition product doesn’t provide the Audit feature.
The following are the descriptions for the graphic charts configured in Audit.
| Field | Description |
|---|---|
| Time when event occurred | Time when the query occurred |
| Log content | Content audit log |
Note
- You can view the DDL, Cluster Monitor, Auth and Entire logs in Audit.
- CRUD Operation Log is not provided because it may cause performance degradation.
- For Enterprise Edition Cluster created before August 18, 2022, Audit can be enabled after restarting DB.
Was this article helpful?