Available in VPC
You can check the history of events that have occurred on the Cloud DB Serverless in Event. The events that occur in DB cluster are saved automatically in the history and stored permanently without requiring additional settings by the user. If you create events by setting notification items and thresholds for each DB cluster, then you can emails and SMS notifications when the events occur.
Event page
The basic descriptions for using Event in VPC are as follows:
| Component | Description |
|---|---|
| ① Menu name | Shows the current menu name. |
| ② Basic features | Check details for Cloud DB Serverless and refresh the Event page |
| ③ **Event Rule settings (Cloud Insight) **button | Go to Cloud Insight, NAVER Cloud Platform's specialized service for monitoring, and set event rules and notifications. |
| ④ Search Date | Check saved event history by designating the event occurrence period |
| ⑤ Search Event | Search event history by DB cluster name and filter conditions. |
| ⑥ Event List | Check saved event history |
View events
To check the events that occurred in Cloud DB Serverless:
- In the VPC environment of the NAVER Cloud Platform console, navigate to
> Services > Database > Cloud DB Serverless. - Click Event.
- When the event list appears, check the required information.
- DBMS: Created DB type
- DB Cluster name: Name of the DB cluster where the event occurred
- Time when event occurred: Time when the event occurred.
- Event type: Type of the event that occurred
- Event name: Name of the event that occurred
- Cluster: Event that occurred in the DB cluster
- Backup: Backup start and end events
- Failover: Event where Primary and Secondary Failovers occured
- Account: DB User creation/deletion/change event
- Scaling in/out: Event where auto-scaling occurred
- Scaling up/down: Event where DB instance specifications changed
- Content: Description of the event that occurred
- Access IP: Access IP address of the admin account where the event occurred.
Set event
You specify event rules and set notifications for each VPC server in the NAVER Cloud Platform Cloud Insight service.
Event Rule settings
If you use Cloud Insight, NAVER Cloud Platform's specialized service for monitoring, then you can set more detailed event rules for DB clusters and monitor them. The events collected by the rules set by the user can be checked from the Cloud Insight dashboard.
For how to set Event Rule on DB clusters in Cloud Insight and check it on Dashboard,see Cloud Insight user guide.
Default Metric indicator
The default Metric indicators you can view in Cloud DB Serverless dashboard in Cloud Insight include the following:
| Graphic chart | Unit | Description |
|---|---|---|
| mysql select qps | query/sec | mysql select qps requests per second |
| mysql insert qps | query/sec | mysql insert qps requests per second |
| mysql update qps | query/sec | mysql update qps requests per second |
| mysql delete qps | query/sec | mysql delete qps requests per second |
| mysql replace qps | query/sec | mysql replace qps requests per second |
| mysql query cache qps | query/sec | mysql query cache qps requests per second |
| mysql procedure call qps | query/sec | mysql procedure call qps requests per second |
| mysql total connection | num | mysql total connection requests |
| mysql running threads | num | mysql running threads requests |
| mysql slow queries | num/min | mysql slow queries requests per minute |
Custom Schema setting items
Metric event monitoring items that can be set in Custom Schema of Cloud Insight include the following:
| Metric | Description | Data type | Aggregation Cycle | Aggregation | Unit |
|---|---|---|---|---|---|
| unit_usage | Instance Unit Usage | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | unit |
| min_unit | Instance Min Unit | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | unit |
| max_unit | Instance Max Unit | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | unit |
| unit_utilization | Unit Utilization | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | % |
| mysql_select | MySQL Select QPS | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
| mysql_insert | MySql Insert QPS | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
| mysql_update | MySQL Update QPS | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
| mysql_delete | MySQL Delete QPS | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
| mysql_replace | MySQL Replace QPS | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
| mysql_qcache | MySQL Query Cache QPS | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
| mysql_call | MySQL Procedure Call QPS | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
| mysql_totalconn | MySQL Total Connection | LONG | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | num |
| mysql_runconn | MySQL Running Connections | LONG | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | num |
| mysql_slow | MySQL Slow Queries | LONG | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | num/min |
| cpu_total | CPU Total | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | core/sec |
| disk_mysql_used | Disk Usage (bytes) | LONG | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | bytes |
| mem_used | Memory Usage (bytes) | LONG | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | bytes |
| network_tx | Network Tx (bytes) | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | bytes/sec |
| network_rx | Network Rx (bytes) | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | bytes/sec |
| disk_read | Disk I/O Read (bytes) | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | bytes/sec |
| disk_write | Disk I/O Write (bytes) | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | bytes/sec |
| mysql_rrps | Row Read Operations Per Second | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
| mysql_wrps | Row Write Operations Per Second | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
| mysql_replication_status | Mysql Replication Status. 0: not replicating, 1: replicating | INTEGER | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | num |
| mysql_replication_delay | Mysql Replication Delay | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | sec |
| mysql_aborted_connects | MySQL Aborted Connections by Server | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | count/min |
| mysql_aborted_clients | MySQL Aborted Connection by Client | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | count/min |
| mysql_innodb_buffer_pool_size | Buffer Pool Size | LONG | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | bytes |
Notification settings
By using Cloud Insight, NAVER Cloud Platform's service product specialized for monitoring, if you have set event rules for DB clusters, you can set thresholds for specific rules and set email and SMS notifications to predetermined users when the thresholds are exceeded.
For how to set Event Rule on DB clusters in Cloud Insight and check it on Dashboard,see Cloud Insight user guide.