Event

Available in Classic

You can check the history of events that have occurred on the Cloud DB for MSSQL server in Event. The events that occur in MSSQL 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 MSSQL server, then you can emails and SMS notifications when the events occur.

Event page

The basics of using the event are as follows.

Area	Description
① Menu name	Name of the menu currently being viewed
② Basic features	Check details for Cloud DB for MSSQL, refresh the Event page.
③ Event History	Check saved event history, search desired event history with event occurrence period and service name.
④ Event settings status	Set event rules (notification items and thresholds), set notification (alarm) recipients and method

Check events

The following describes how to check the events that occurred in an MSSQL server.

1. From the Classic environment of the NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL 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 service name: Name of the MSSQL Service where the event occurred
   • DB Server name: Name of the MSSQL server where the event occurred
   • Event occurrence time: time when the event occurred
   • Event type: type of the event that occurred
     • MSSQL Server: Events that have occurred in the DB server
     • Monitoring: event for which a user registers or removes DB server events
   • Event name: name of the event that occurred
     • Backup: backup start
     • Restore: restoration start
     • Mirroring: configure mirroring (HA)
     • Failover: failover occurrence
       • When a failure occurred in the principal server and triggered a failover
       • When the user restarted the server with the failover option
     • Account: DB account creation
     • AgentJob: new SqlAgentJob created
       • When the user created a new batch job
       • When its newly created on a new server due to specification adjustment, etc.
     • Restart: restart DB server
     • LogShipping: LogShipping start
     • Set event: registration of event that needs notifications
     • Pause notifications: suspend event notifications
     • Resume notifications: the temporarily paused event notifications have been resumed.
     • Alarm notification: deliver notifications
   • 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 MSSQL server, then click it to see the details.
   
   • DB service name: service name of the MSSQL server
   • DB status: status of the MSSQL server in operation
   • DB Role: the role of the MSSQL server in operation
   • Creation date: date that MSSQL server in operation was created

Set event

You can set events so that users can be notified when a specified situation occurs in the MSSQL server.

Note

For providing better services, we plan to replace the data collection module related to Event settings.
Due to the replacement of modules with new ones, the functions of event settings/cancellation/notification pause/notification restart which used to be provided on the Event screen have been to transferred to Cloud Insight.
The notification items separately set in the DB cluster are not automatically transferred, so if you have any such item, you can reconfigure it through the Event Rule Settings function of Cloud Insight between September 7 and October 12.

If you use Cloud Insight, NAVER Cloud Platform's specialized service for monitoring, then you can set more detailed event rules for MSSQL servers and monitor them. The events collected by the rules set by the user can be checked from the Cloud Insight dashboard.

For information on setting event rules for MSSQL servers, checking them on the dashboard, and setting event rule notifications by MSSQL server in Cloud Insight, see Cloud Insight User Guide.

Set event

You specify event rules and set notifications for each MSSQL server in the NAVER Cloud Platform console.

The following describes how to set up events of an MSSQL server.

1. From the Classic environment of the NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.

2. Click the Event menu.

3. Click the Event settings status tab, and then click the MSSQL 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.
   

   Notification item	Detailed notification item	Description
   CPU used	% Processor Time	CPU usage (%)
   CPU Privilege	% Privilege Time	Kernel CPU usage (%)
   CPU Queue	Processor Queue Length	Number of pending threads on the CPU queue
   Context Switches	Context Switches/sec	Number of processor switches made from one thread to another
   disk read latency	Avg. Disk Sec/Read	Average time it takes to read the disk
   disk write latency	Avg. Disk Sec/Write	Average time it takes to write on the disk
   disk queue length	disk Queue Length	Number of pending threads on the disk queue
   disk read mbyte	Disk read Mbyte/sec	How much the disk reads per second (MB)
   disk write mbyte	Disk write Mbyte/sec	How much is written to the disk per second (MB)
   memory free megabyte	FREE MegaByte	Free memory capacity not in use (MB)
   network in	Byte Received/sec	Number of bytes sent on the network (bytes)
   network out	Byte Send/sec	Number of bytes received on the network (bytes)
   network packet	Packets/sec	Number of packets sent on the network (bytes)
   DB lazy write	Lazy writes/sec	Number of buffers recorded by the buffer manager's lazy writer
   Free Pages	Free Pages	Available number of pages
   Free Memory	Free Memory	Available memory capacity (KB)
   Page Life Expectancy	Page Life Expectancy	Number of seconds a DB data page will stay in the buffer pool without references
   memorygrantpending	Memory Grants Pending	Total number of processes waiting to be granted workspace memory
   query per second	Batch Requests/sec	Number of queries processed per second
   DB buffer lookup	Page lookups/sec	Number of requests per second to find a page in the buffer pool
   DB buffer reads	Page reads/sec	Number of physical database page reads that are executed per second
   DB buffer writes	Page writes/sec	Number of physical database page writes that are executed per second
   latch wait	Total Latch Wait Time	Total latch wait time for latch requests in the last second (ms)
   lock wait	Lock Wait Time	Total wait time for locks in the last second (ms)
   compile	SQL Compilations/sec	Number of compilations per second
   re-compile	SQL Re-Compilations/sec	Number of re-compilations per second
   connections	User Connections	Number of current connections
   failover (master server down)		Switchover to the mirror server due to principal server failure
   recreation (slave server down)		Recreate the mirror server due to mirror server failure
   restart with failover		Switchover to the mirror server due to principal server restart
   restart without failover		Restart the mirror server

   • You can modify or delete the notification items by clicking the [Modify] or [Delete] button.

6. Click the [Next] button.

7. Select the recipient for occurred notifications and notification method, and then click the [Add] button.
   

   • You can click the [Delete] button to delete a notification recipient added.
   • If there's no notification recipient registered, click the [Manage notification recipients] button, and then add new recipients.

8. 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 event

The following describes how to remove set events.

1. From the Classic environment of the NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.
2. Click the Event menu.
3. Click the Event settings status tab, and then click the MSSQL server you want to remove events from.
4. Remove events as shown below.
   • Delete individual event: From the event list displayed under the row of the selected MSSQL 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 Classic environment of the NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.
2. Click the Event menu.
3. Click the Event settings status tab, and then click the MSSQL 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 MSSQL server's row, and view the list of notification recipients.
     • Click the [Add] or [Delete] button to add or delete notification recipients.
     • Click the [Manage notification recipients] button to add new notification recipients.
   • 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.