--- title: "Event" slug: "database-database-11-6" tags: ["Cloud DB for MongoDB", "VPC"] updated: 2026-09-17T09:25:07Z published: 2026-09-17T09:25:07Z canonical: "guide.ncloud-docs.com/database-database-11-6" stale: true --- > ## 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. # Event Available in VPC In Event, you can view the event history generated on Cloud DB for MongoDB servers. Events generated in MongoDB are automatically recorded and retained permanently without any additional configuration by you. ## Event interface The following describes the basic elements of the Event interface: ![clouddbformongodb-event-screen_vpc_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/clouddbformongodb-event-screen_vpc_en.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A49%3A07Z&se=2026-10-27T17%3A49%3A07Z&sr=c&sp=r&sig=eWOD6%2F3hYAT1C%2FPshRcQUoK7iRe0w1LWGBqgYs%2F%2BqAA%3D) | Component | Description | | --- | --- | | ① Menu name | Show the current menu name. | | ② Basic features | View Cloud DB for MongoDB details and refresh the Event interface. | | ③ Event rule configuration | Move to Cloud Insight, the monitoring service of the NAVER Cloud Platform, to configure event rules and notifications (alarms). | | ④ Event list | View stored event history and search for specific events by occurrence period and service name in the event list. | ## View events To view events generated in MongoDB: 1. In the VPC environment of the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Database** > **Cloud DB for MongoDB**. 2. Click **Event**. 3. When the event list appears, review the required information. | Event name | Event details | Event example | | --- | --- | --- | | DB | Shard expansion | shard has been added | | DB | Mongos server count change | mongos server count has been changed | | DB | Config server count change | config server count has been changed | | DB | Secondary server count change | secondary server count has been changed | | DB | Arbiter server count change | arbiter server count has been changed | | DB | Storage capacity change | Data Storage Size Has Been Changed : 10 GB | | DB | Version upgrade | Version Upgrade (MongoDB 4.4.18 Enterprise Edition) | | Backup | Backup completed | Backup Complete | | Backup | Backup deleted | Delete Backup (March 08, 2023) | | Backup | Backup configuration change (time, retention, speed) | Change Backup config / 1 Days (01:00) (parallel: 4) | | Account | Account added | DB account dbname.username has been added | | Account | Account password changed | DB acoount dbname.username has been changed | | Account | Account permission changed | DB acoount dbname.username has been changed | | Account | Account deleted | DB acoount dbname.username has been deleted | | fail-over | Failover performed due to a "Primary DB Failover" request | fail over: mg-0000000-mb001-abcd | - **DB service name**: The name of the MongoDB service where the event occurred - **DB Server name**: The name of the MongoDB server where the event occurred - **Event occurrence time**: The time when the event occurred - **Event type**: The type of event that occurred - **Event name**: The name of the event that occurred - **Details**: A description of the event 4. Click an event to view detailed information. ![clouddbformongodb-event-list_vpc_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/clouddbformongodb-event-list_vpc_en.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A49%3A07Z&se=2026-10-27T17%3A49%3A07Z&sr=c&sp=r&sig=eWOD6%2F3hYAT1C%2FPshRcQUoK7iRe0w1LWGBqgYs%2F%2BqAA%3D) - **DB service name**: The service name of the MongoDB server - **DB status**: The status of the running MongoDB server - **Cluster Type**: The cluster type of the running MongoDB server - **DB Role**: The role of the running MongoDB server - **Creation date and time**: The date and time when the MongoDB server was created ## Event rule configuration By using Cloud Insight, the monitoring service of the NAVER Cloud Platform, you can configure event rules for MongoDB servers in more detail for monitoring. Events collected according to the rules you configure are available on the Cloud Insight dashboard. Caution Additional charges apply when you subscribe to Cloud Insight. For information about Cloud Insight and its pricing plans, see [**Services > Management & Governance > Cloud Insight**](https://www.ncloud.com/product/management/cloudInsight) on the NAVER Cloud Platform portal. For instructions on configuring event rules for MongoDB servers and viewing them on the dashboard, see the [Cloud Insight user guide](/docs/en/cloudinsight-cloudinsightconsole). ## Configure notifications (alarms) When you use Cloud Insight, the monitoring service of the NAVER Cloud Platform, you can configure thresholds for specific event rules for MongoDB servers and set notifications (alarms) to be sent by email and SMS to predefined users when the thresholds are exceeded. Caution Additional charges apply when you subscribe to Cloud Insight. For information about Cloud Insight and its pricing plans, see [**Services > Management & Governance > Cloud Insight**](https://www.ncloud.com/product/management/cloudInsight) on the NAVER Cloud Platform portal. For instructions on configuring notifications (alarms) for event rules by MongoDB server in Cloud Insight, see the [Cloud Insight user guide](/docs/en/cloudinsight-cloudinsightconsole).