- Print
- PDF
Event
- Print
- PDF
Available in Classic and VPC
In Event, you can check the history of events that occurred in the Cloud DB for MySQL server. The events that occur in MySQL 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 MySQL Server, then you can emails and SMS notifications when the events occur.
Event page (VPC)
The basics of using events in the VPC environment are as follows.
Area | Description |
---|---|
① Menu name | Name of the menu currently being checked |
② Basic features | Check details for Cloud DB for MySQL, refresh the event page |
③ Set event rules (Cloud Insight) | Go to NAVER Cloud Platform's Cloud Insight, a service specialized for monitoring, and set event rules and notification |
④ Event list | Check saved event history, search desired event history with event occurrence period and service name from the event list |
Event page (Classic)
The basics of using events in the Classic environment are as follows.
Area | Description |
---|---|
① Menu name | Name of the menu currently being checked |
② Basic features | Check details for Cloud DB for MySQL, refresh the event page |
③ Event history, event settings status | Check saved event history, search desired event history with event occurrence period and service name from the event list, set events |
④ Event list | Check the event list and settings |
Check events (VPC)
The following describes how to check the events that occurred in the MySQL Server of the VPC environment.
- From the NAVER Cloud Platform console's VPC environment, click the Services > Database > Cloud DB for MySQL menus, in that order.
- Click the Event menu.
- When the event list appears, check the required information.
- DB Server name: Name of the MySQL Server where the event occurred
- Event occurrence time: Time when the event occurred
- Event type: Type of the event that occurred
- Event name: Name of the event that occurred
- DB: Events that occurred in DB
- Backup: Start or end events of backup
- Storage Size: Change of storage size
- Failover: Events that occurred upon failover
- Content: Description of the event that occurred
- Access IP: Access IP address of the admin account where the event occurred
- If the event type is DB Server, then click it to see the details.
- DB service name: Service name of the MySQL Server
- DB status: Status of the MySQL Server in operation
- DB role: Role of the MySQL Server in operation
- Creation date: Date that MySQL Server in operation was created
- DB engine version: DB engine version
Check events (Classic)
The following describes how to check the events that occurred in the MySQL Server of the Classic environment.
- From the NAVER Cloud Platform console's Classic environment, click the Services > Database > Cloud DB for MySQL menus, in that order.
- Click the Event menu.
- Click the Event History tab, and check the necessary information when the event list appears.
- DB Server name: Name of the MySQL Server where the event occurred
- Event occurrence time: Time when the event occurred
- Event type: Type of the event that occurred
- Event name: Name of the event that occurred
- DB: Events that occurred in DB
- Backup: Start or end events of backup
- Storage Size: Change of storage size
- Failover: Events that occurred upon failover
- Content: Description of the event that occurred
- Access IP: Access IP address of the admin account where the event occurred
- If the event type is DB Server, then click it to see the details.
- DB service name: Service name of the MySQL Server
- DB status: Status of the MySQL Server in operation
- DB role: Role of the MySQL Server in operation
- Creation date: Date that MySQL Server in operation was created
- DB engine version: DB engine version
Set events (VPC)
You can utilize the NAVER Cloud Platform's Cloud Insight to specify event rules of MySQL Server in the VPC environment, and set notifications.
Set event rules (VPC)
If you use Cloud Insight, NAVER Cloud Platform's service specialized for monitoring, then you can set more detailed event rules for MySQL Servers and monitor them. The events collected by the rules set by the user can be checked from the Cloud Insight dashboard.
Additional charges apply when you request subscription to Cloud Insight. For the introduction on Cloud Insight and details about its pricing plans, refer to the Service > Management > Cloud Insight menu in the NAVER Cloud Platform portal.
Please refer to the Cloud Insight Guide for information on setting event rules for MySQL Servers and checking them on the dashboard in Cloud Insight.
Basic metric indicators
The basic metric indicators that can be checked from the MySQL Server dashboard of Cloud Insight are as follows.
Graphic chart | Unit | Description |
---|---|---|
mysql select qps | query/sec | mysql insert request amount per second |
mysql insert qps | query/sec | mysql insert qps request amount per second |
mysql update qps | query/sec | mysql update qps request amount per second |
mysql delete qps | query/sec | mysql delete qps request amount per second |
mysql replace qps | query/sec | mysql replace qps request amount per second |
mysql query cache qps | query/sec | mysql query cache qps request amount per second |
mysql procedure call qps | query/sec | mysql procedure call qps request amount per second |
mysql total connection | query/sec | mysql total connection request amount per second |
mysql running threads | num | mysql running threads request amount per second |
mysql slow queries | query/sec | mysql slow queries request amount per second |
Custom schema configuration items
The metric event monitoring items that can be configured in the Custom schema menu of Cloud Insight are as follows.
Metric | Description | Data type | Aggregation Cycle | Aggregation | Unit |
---|---|---|---|---|---|
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 | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
mysql_runconn | mysql running threads | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | num |
mysql_slow | mysql slow queries | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
cpu_user | CPU user | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | % |
cpu_sys | CPU kernel | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | % |
cpu_iowait | CPU iowaitd | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | % |
cpu_total | CPU Total | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | % |
cpu_load_1 | Load avg 1min | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | % |
cpu_load_5 | Load avg 5min | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | % |
cpu_load_15 | Load avg 15min | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | % |
disk_mysql_used | mysql disk used | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | bytes |
mem_pct | Memory used | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | % |
nic_tx | nic send | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | bytes/60 |
nic_rx | nic receive | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | bytes/60 |
nic_total | nic total | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | bytes/60 |
swap_pct | Swap used | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | % |
disk_read | Disk I/O Read bytes | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | KB/sec |
disk_write | Disk I/O Write bytes | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | KB/sec |
disk_total | Disk I/O Total Byte | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | KB/sec |
cpu_pct | CPU used | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | % |
mysql_rqps | mysql row read | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
mysql_wqps | mysql row write | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
mysql_slaverun | mysql replication stop | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | sec |
mysql_slavedelay | mysql replication delay | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | sec |
mysql_rrps | read rowaccess | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
mysql_wrps | write rowaccess | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | query/sec |
mysql_ibtmp | InnoDB Temporary Size | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | MB |
mysql_active | Could not connect (0 or 100) | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | num |
disk_mysql_free | Free StorageSpace | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | KB |
mem_free | Free Memory | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | KB |
mysql_total_binlog_size | Total Binary Log Size | FLOAT | Min1,Min5,Min30,Hour2,Day1 | AVG,MAX,MIN,SUM,COUNT | GB |
Notification settings (VPC)
By using Cloud Insight, NAVER Cloud Platform's service specialized for monitoring, if you have set event rules for MySQL Servers, then you can set thresholds for specific rules and set email and SMS notifications to predetermined users when the thresholds are exceeded.
Additional charges apply when you request subscription to Cloud Insight. For the introduction on Cloud Insight and details about its pricing plans, refer to the Service > Management > Cloud Insight menu in the NAVER Cloud Platform portal.
Please refer to the Cloud Insight Guide for information on setting notifications for event rules by MySQL Server in Cloud Insight.
Set events (Classic)
You can set events so that users can be notified when a specified situation occurs in the MySQL Server.
Set events
You specify event rules and set notifications for each MySQL Server in the NAVER Cloud Platform console.
The following describes how to set up events of a MySQL Server in the Classic environment.
- From the NAVER Cloud Platform console's Classic environment, click the Services > Database > Cloud DB for MySQL menus, in that order.
- Click the Event menu.
- Click the Event settings status tab, and then click the MySQL Server you want to set events for.
- Click the [Set events] > [Set event items] buttons, in that order.
- Select an item by referring to the table shown below, enter the threshold that will cause notifications, and then click the [Add] button.
Notification item Detailed notification item Description CPU ① Used(%)
② Iowait(%)① CPU usage
② CPU IOwait usageMemory Used(%) Memory usage Swap swap_pct Generated swap memory Disk I/O ① Read kbytes
② Write kbytes① Disk read actions
② Disk write actionsLoad Average 1min, 5min, 15min Server load Filesystem Used(kByte) Disk usage Connections Running Number of MySQL Server access sessions SlowQuery SlowQueryCount Number of queries executed for 1 second or longer Replication ① Stop
② Delay① Replication suspension information
② Replication latency against the masterDB Down DB down information - You can modify or delete the added events by clicking the [Modify] or [Delete] button.
- Click the [Next] button.
- Add the recipient for occurred notifications, select the notification method, and then click the [Add] button.
- You can modify or delete the added events by clicking the [Modify] or [Delete] button.
- Click the [Next] button, check the settings, and then click the [OK] button.
Manage events
You can check the content and notification recipients of the set events, suspend or restart notifications, or remove events.
Remove events
The following describes how to remove set events.
- From the NAVER Cloud Platform console's Classic environment, click the Services > Database > Cloud DB for MySQL menus, in that order.
- Click the Event menu.
- Click the Event settings status tab, and then click the MySQL Server you want to remove events from.
- Remove events as shown below.
- Delete individual events: From the event list displayed under the row of the selected MySQL Server, find the event you want to delete, click the [Delete] button, and then click the [Yes] button from the confirmation pop-up window.
- Delete all events from the server: Click the [Remove events] button, and then click the [Yes] button from the confirmation pop-up window.
Manage notifications
You can check the notification recipients for the occurrence of event notifications, and suspend or restart notifications. If you suspend notifications, then the notifications are not sent, even when the events occur for the set period.
You can manage notifications as follows.
- From the NAVER Cloud Platform console's Classic environment, click the Services > Database > Cloud DB for MySQL menus, in that order.
- Click the Event menu.
- Click the Event settings status tab, and then click the MySQL Server you want to check event notifications for.
- Manage event notifications settings as shown below.
- Manage notification recipients: Click the [View] button of the selected MySQL Server's row, and manage notification recipients from the settings pop-up window.
- Suspend notifications: Click the [Suspend notifications] button, enter the period and the registrant, and then click the [Set] button.
- Restart notifications: Click the [Restart notifications] button, and then click the [Yes] button from the confirmation pop-up window.