Event

Available in VPC

You can view the history of events that have occurred on the Cloud DB for MySQL Server in Event. 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 receive emails and SMS notifications when the events occur.

Event interface

The basic descriptions for using Event in VPC are as follows:

Component	Description
① Menu name	Current menu name.
② Basic features	Check details for Cloud DB for MySQL and refresh the Event interface.
③ Event Rule settings (Cloud Insight)	Go to Cloud Insight, NAVER Cloud Platform's specialized service for monitoring, and set event rules and notifications.
④ Event list	View stored event history and search for specific events by occurrence period and service name in the event list.

View events

To check the events that occurred on the MySQL Server in VPC, follow these steps:

In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MySQL.
Click Event.
When the event list appears, check the required information.
- DB Server name: The name of the MySQL Server where the event occurred.
- Time when event occurred: Time when the event occurred.
- Event type: The type of event that occurred.
- Event name: The name of the event that occurred.
  - DB: Event that occurred in the DB.
  - Backup: Backup start and end events.
  - StorageSize: Storage contract capacity.
  - Failover: Event that occurred during failover.
  - Config Template: Event that occurred in the config template.
- 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: The service name of the MySQL Server
- DB status: The status of the running MySQL Server
- DB Role: The role of the running MySQL Server
- Creation date: The date when the running MySQL Server was created
- DB engine version: DB engine version

Set event

You can specify event rules and set notifications for MySQL Server in the VPC environment through NAVER Cloud's Cloud Insight.

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 MySQL Servers and monitor them. Events collected according to the rules you configure are available on the Cloud Insight dashboard.

Caution

Additional fees apply when you subscribe to Cloud Insight. For more information on Cloud Insight introduction and pricing, see Services > Management & Governance > Cloud Insight on the NAVER Cloud Platform portal.

For more information on how to set Event Rule on MySQL Server in Cloud Insight and check it on the dashboard, see Cloud Insight user guide.

Default Metric indicator

The default Metric indicators you can view in the MySQL Server 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
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 (active(100) or inactive(0))	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

By using Cloud Insight, NAVER Cloud Platform's service product specialized for monitoring, if you have set Event Rules for MySQL Servers, you can set thresholds for specific rules and set email and SMS notifications for predetermined users when the thresholds are exceeded.