Event
    • PDF

    Event

    • PDF

    Article Summary

    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.

    database-database-5-5_eventmain_vpc_en(1).png

    AreaDescription
    ① Menu nameName of the menu currently being checked
    ② Basic featuresCheck 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 listCheck 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.

    database-database-5-5_eventmain_vpc_en.png

    AreaDescription
    ① Menu nameName of the menu currently being checked
    ② Basic featuresCheck details for Cloud DB for MySQL, refresh the event page
    ③ Event history, event settings statusCheck saved event history, search desired event history with event occurrence period and service name from the event list, set events
    ④ Event listCheck 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.

    1. From the NAVER Cloud Platform console's VPC environment, click the Services > Database > Cloud DB for MySQL menus, in that order.
    2. Click the Event menu.
    3. 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
    4. If the event type is DB Server, then click it to see the details.
      database-database-5-5_eventdetails_vpc_en(1).png
      • 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.

    1. From the NAVER Cloud Platform console's Classic environment, click the Services > Database > Cloud DB for MySQL menus, in that order.
    2. Click the Event menu.
    3. 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
    4. If the event type is DB Server, then click it to see the details.
      database-database-5-5_eventdetails_en.png
      • 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.

    Caution

    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 chartUnitDescription
    mysql select qpsquery/secmysql insert request amount per second
    mysql insert qpsquery/secmysql insert qps request amount per second
    mysql update qpsquery/secmysql update qps request amount per second
    mysql delete qpsquery/secmysql delete qps request amount per second
    mysql replace qpsquery/secmysql replace qps request amount per second
    mysql query cache qpsquery/secmysql query cache qps request amount per second
    mysql procedure call qpsquery/secmysql procedure call qps request amount per second
    mysql total connectionquery/secmysql total connection request amount per second
    mysql running threadsnummysql running threads request amount per second
    mysql slow queriesquery/secmysql 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.

    MetricDescriptionData typeAggregation CycleAggregationUnit
    mysql_selectmysql select qpsFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTquery/sec
    mysql_insertmysql insert qpsFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTquery/sec
    mysql_updatemysql update qpsFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTquery/sec
    mysql_deletemysql delete qpsFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTquery/sec
    mysql_replacemysql replace qpsFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTquery/sec
    mysql_qcachemysql query cache qpsFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTquery/sec
    mysql_callmysql procedure call qpsFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTquery/sec
    mysql_totalconnmysql total connectionFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTquery/sec
    mysql_runconnmysql running threadsFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTnum
    mysql_slowmysql slow queriesFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTquery/sec
    cpu_userCPU userFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNT%
    cpu_sysCPU kernelFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNT%
    cpu_iowaitCPU iowaitdFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNT%
    cpu_totalCPU TotalFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNT%
    cpu_load_1Load avg 1minFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNT%
    cpu_load_5Load avg 5minFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNT%
    cpu_load_15Load avg 15minFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNT%
    disk_mysql_usedmysql disk usedFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTbytes
    mem_pctMemory usedFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNT%
    nic_txnic sendFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTbytes/60
    nic_rxnic receiveFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTbytes/60
    nic_totalnic totalFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTbytes/60
    swap_pctSwap usedFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNT%
    disk_readDisk I/O Read bytesFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTKB/sec
    disk_writeDisk I/O Write bytesFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTKB/sec
    disk_totalDisk I/O Total ByteFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTKB/sec
    cpu_pctCPU usedFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNT%
    mysql_rqpsmysql row readFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTquery/sec
    mysql_wqpsmysql row writeFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTquery/sec
    mysql_slaverunmysql replication stopFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTsec
    mysql_slavedelaymysql replication delayFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTsec
    mysql_rrpsread rowaccessFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTquery/sec
    mysql_wrpswrite rowaccessFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTquery/sec
    mysql_ibtmpInnoDB Temporary SizeFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTMB
    mysql_activeCould not connect (0 or 100)FLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTnum
    disk_mysql_freeFree StorageSpaceFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTKB
    mem_freeFree MemoryFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTKB
    mysql_total_binlog_sizeTotal Binary Log SizeFLOATMin1,Min5,Min30,Hour2,Day1AVG,MAX,MIN,SUM,COUNTGB

    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.

    Caution

    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.

    database-database-5-5_setevent1_en.png

    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.

    1. From the NAVER Cloud Platform console's Classic environment, click the Services > Database > Cloud DB for MySQL menus, in that order.
    2. Click the Event menu.
    3. Click the Event settings status tab, and then click the MySQL Server you want to set events for.
    4. Click the [Set events] > [Set event items] buttons, in that order.
    5. Select an item by referring to the table shown below, enter the threshold that will cause notifications, and then click the [Add] button.
      database-database-5-5_setevent2_en.png

      Notification itemDetailed notification itemDescription
      CPU① Used(%)
      ② Iowait(%)
      ① CPU usage
      ② CPU IOwait usage
      MemoryUsed(%)Memory usage
      Swapswap_pctGenerated swap memory
      Disk I/O① Read kbytes
      ② Write kbytes
      ① Disk read actions
      ② Disk write actions
      Load Average1min, 5min, 15minServer load
      FilesystemUsed(kByte)Disk usage
      ConnectionsRunningNumber of MySQL Server access sessions
      SlowQuerySlowQueryCountNumber of queries executed for 1 second or longer
      Replication① Stop
      ② Delay
      ① Replication suspension information
      ② Replication latency against the master
      DBDownDB down information
      • You can modify or delete the added events by clicking the [Modify] or [Delete] button.
    6. Click the [Next] button.
    7. Add the recipient for occurred notifications, select the notification method, and then click the [Add] button.
      database-database-5-5_setevent3_en.png
      • You can modify or delete the added events by clicking the [Modify] or [Delete] button.
    8. Click the [Next] button, check the settings, and then click the [OK] button.
      database-database-5-5_setevent4_en.png

    Manage events

    You can check the content and notification recipients of the set events, suspend or restart notifications, or remove events.

    database-database-5-5_manageevent_en.png

    Remove events

    The following describes how to remove set events.

    1. From the NAVER Cloud Platform console's Classic environment, click the Services > Database > Cloud DB for MySQL menus, in that order.
    2. Click the Event menu.
    3. Click the Event settings status tab, and then click the MySQL Server you want to remove events from.
    4. 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.

    1. From the NAVER Cloud Platform console's Classic environment, click the Services > Database > Cloud DB for MySQL menus, in that order.
    2. Click the Event menu.
    3. Click the Event settings status tab, and then click the MySQL Server you want to check event notifications for.
    4. 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.

    Was this article helpful?

    Changing your password will log you out immediately. Use the new password to log back in.
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.