Documentation Index

Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt

Use this file to discover all available pages before exploring further.

Monitoring

Prev Next

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. Monitoring provides the following dashboards:

  • DB Dashboard: Monitoring information for running MongoDB servers.
  • OS Dashboard: Operation system for running MongoDB servers.
  • DB Logs: Timestamps and details of all logs generated by running MongoDB servers.
  • Query Timeline: Query execution history for running MongoDB servers.
  • Audit: Records the time and content of Audit logs generated by the MongoDB Server in operation.

You can check the performance information of the MongoDB Server within the last 1 year based on average values, and logs and queries from the last 4 weeks through these five types of dashboards. Each dashboard consists of multiple graph charts. You can print specific charts or download them to your local PC in various extensions for effective use.

Note

You can set the user to be notified when monitoring results show that a certain metric 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 interface

The basics of using Monitoring are as follows:

clouddbformongodb-monitoring-screen_vpc_ko

Component Description
① Menu name Current menu name.
② Basic features Check details for Cloud DB for MongoDB, refresh the Monitoring interface.
③ 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:

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MongoDB.

  2. Click the Monitoring menu.

  3. Click the MongoDB Server to be monitored from the list of MongoDB Service.

  4. Click the button for the dashboard you want to check from the interface on the right.

  5. Click and select all graphic charts you want to display and check on the dashboard.

  6. From the period or view time selection box, click and select the period you want to view, or enter it directly.

  7. Check the results from the dashboard.

    • If you want 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 view a detailed graph: Double-click the graph chart.
    • Print a graph chart: Select clouddbforpostgresql-monitoring_ico-03 to click Print chart.
    • Download a graph chart to your local PC: Select clouddbforpostgresql-monitoring_ico-03 and click the file extension menu to download.
      • Download PNG image: An image file with a PNG extension.
      • Download JPEG image: An image file with a JPEG extension.
      • Download PDF document: A document file with a PDF extension.
      • Download SVG vector image: A vector image file with an SVG extension.
      • Download CSV: A document file with a CSV extension.
Caution
  • In Step 5, the default setting is select all, and in Step 6, the default time range is the past 1 hour.
  • In Step 6, the period can be selected up to 1 year for DB Dashboard or OS Dashboard, and up to 4 weeks for DB Logs or Query Timeline.
Note

Navigate to Menu > Services > Database > Cloud DB for MongoDB > DB Server, select the desired server, and click [Monitoring] to go directly to the interface in Step 4.

DB Dashboard graph charts

The following are some descriptions for the graphic charts configured in DB Dashboard:

clouddbformongodb-monitoring-dbdashchart_vpc_ko

clouddbformongodb-monitoring-dbdashchart1_vpc_ko

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 Index utilization metric.
  • scan and order: Number of queries that could not use an index for sorting.
  • scanned document: Number of times a document scan occurred for query execution.
  • scanned index: Number of index scans performed to execute queries.
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 graph charts

The following are some descriptions for the graphic charts configured in OS Dashboard:

clouddbformongodb-monitoring-osdashchart_vpc_ko

Graphic chart Unit Description
CPU Usage used(%) CPU usage.
Load Average - Server load.
Memory Usage used(%) Memory usage.
Swap used(%) Swap memory usage.
Disk Used GB Disk usage.
Disk I/O MB / sec Disk input/output per second.
Network I/O MB / sec Network input/output per second.

DB Logs graph charts

The following are the descriptions for the graphic charts configured in DB Logs:

clouddbformongodb-monitoring-dblogchart_vpc_ko

Field Description
Time when event occurred Time when the DB log occurred.
Log content DB log details.
Note

In DB Logs, you can check the Slow Query log, Login log, Entire log of the MongoDB Server in operation.

Query Timeline graph charts

The following are the descriptions for the graphic charts configured in the Query Timeline:

clouddbformongodb-monitoring-querychart_vpc_ko

Field Description
Time when event occurred Time when the query occurred.
Log content Content of the executed query.

Audit graphic chart

Audit feature is provided by the Enterprise Edition.
Community Edition doesn't provide the Audit feature.
The following are the descriptions for the graphic charts configured in Audit:
clouddbformongodb-monitoring-auditchart_vpc_ko

Field Description
Time when event occurred Time when the query occurred.
Log content Audit Log content.
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.
Business Registration Number: 129-86-31394 E-commerce Permit Number:No. 2009-GyeonggiSeongnam-0510
CEO: Kim Yuwon Address: NAVER Green Factory 17th–26th Floors, Buljeong-ro 6, Bundang-gu, Seongnam-si, Gyeonggi-do 13561, Republic of Korea. Customer Support Number: 1544-5876
© NAVER Cloud Corp. All Rights Reserved.