Cloud Eye. User Guide. Issue 13. Date

Transcription

1 Issue 13 Date

2 Contents Contents 1 Introduction What Is Cloud Eye? Functions Application Scenarios Related Services User Permissions Region Projects Getting Started Operation Guide Dashboard Instance Monitoring Alarm FAQs What Is Cloud Eye? Which Metrics Can Be Monitored by CES? What Alarm Status Does CES Support? What Is an Alarm Notification? How Many Types of Alarm Notifications Exist? How Can I Configure Them? How Can I Add Customized Monitoring Metrics? Why Are the Network Traffic Metrics in CES Different from Those Detected in ECS? What Is Rollup? How Long Are the Metric Data Retained? What Are the Effects on ECS Monitoring Metrics If VM Tools Is Not Installed on ECSs? How Can I Export Monitoring Data? How Many Rollup Methods Does CES Support? Under What Circumstances Will an Alarm Rule Trigger "Insufficient data"? A Change History Issue 13 ( ) ii

3 1 Introduction 1 Introduction 1.1 What Is Cloud Eye? Cloud Eye (CES) is an open monitoring platform that provides monitoring, alarm reporting, and alarm notifications for your resources. CES can monitor metrics of the following services: Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Virtual Private Cloud (VPC), Relational Service (RDS), Elastic Load Balance (ELB), Auto Scaling (AS), Distributed Message Service (DMS), Distributed Cache Service (), and Workspace. You can add alarm rules and configure alarm notification policies to learn the running status and performance of service instances in a timely manner. Table 1-1 describes the functions provided by CES. Table 1-1 CES functions Function Dashboard Description Displays the number of metrics for each service monitored by CES. You can add or delete monitored metrics. You can choose from the following service metrics. ECS: CPU Usage, Disk Read Rate, Disk Read Requests, Disk Usage, Disks Write Rate, Disks Write Requests, Memory Usage, Inband Incoming Rate, Inband Outgoing Rate, Outband Incoming Rate, System Status Check Failed, and Outband Outgoing Rate EVS: Disks Read Rate, Disks Write Rate, Disks Read Requests, and Disks Write Requests AS: CPU Usage, Memory Usage, Instance Qty., Inbound Rate, and Outbound Rate ELB: cps, Active Connections, Inactive Connections, New cps, Inbound Packets, Outbound Packets, Inbound Rate, Outbound Rate, Abnormal Hosts, and Normal Hosts VPC: Upstream Bandwidth, Downstream Bandwidth, Upstream Traffic, and Downstream Traffic DMS: Accumulated Messages, Consumed Messages, Skipped Messages, Queued Messages, Message Size (byte), Available Dead Letter Messages, Historical Dead Letter Messages, and Request Count : CPU Usage, Memory Usage, Network Input Throughput, Issue 13 ( ) 1

4 1 Introduction Function Instance monitoring Alarm Description Network Output Throughput, Connected Clients, Client Longest Output List, Client Biggest Input Buf, Blocked Clients, Used Memory, Used Memory RSS, Used Memory Peak, Used Memory Lua, Memory Fragmentation Ratio, Total Connections Received, Total Commands Processed, Instantaneous Ops Per Second, Total Net Input Bytes, Total Net Output Bytes, Instantaneous Input Kbps, Instantaneous Output Kbps, Rejected Connections, Sync Full, Sync Partial OK, Sync Partial Err, Expired Keys, Evicted Keys, Keyspace Hits, Keyspace Misses, PubSub Channels, PubSub Patterns, Aof Current Size, and Latest Fork usec RDS: Disk Usage, CPU Usage, Memory Usage, Input/output operations per second (IOPS), Network Input Throughput, Network Output Throughput, Total Connections, Current Active Connections, Query Per Second (QPS), transactions per second (TPS), Buffer Pool Usage, Buffer Pool Hit Rate, Buffer Pool Dirty Block Rate, InnoDB Read Throughput, InnoDB Write Throughput, InnoDB File Read Frequency, InnoDB File Write Frequency, InnoDB Log Write Request Frequency, InnoDB Log Physical Write Frequency, InnoDB Log fsync() Write Frequency, Temporary Tables Qty, Key Buffer Usage, Key Buffer Write Hit Rate, Key Buffer Read Hit Rate, MyISAM Disk Write Speed, MyISAM Disk Read Speed, MyISAM Buffer Pool Write Speed, MyISAM Buffer Pool Read Speed, Delete Execute Speed, Insert Execute Speed, Insert_Select Execute Speed, Replace Execute Speed, Replace_Selection Execute Speed, Select Execute Speed, Update Execute Speed, Row Delete Speed, Row Insert Speed, Row Read Speed, Row Update Speed, Transaction Logs Usage, Replication Slot Usage, Connections, Maximum Used Transaction IDs, Transaction Logs Generations, Oldest Replication Slot Lag, Replication Lag, Total Disk Size, Disk Usage, Disk Read Throughput, Disk Write Throughput, Average Time Read per Disk, Average Time Write per Disk, Average Disk Queue Length, and Number of Connections In Use Workspace: CPU Usage, Memory Usage, Disk Usage, Input/output operations per second (IOPS), Network Input Throughput, and Network Output Throughput If you have signed up for one or more of the following services: ECS, EVS, VPC, ELB, AS, Workspace,, DMS, or RDS, you can use CES to view the status of service instances without installing additional plug-ins. Adds, views, modifies, deletes, enables, or disables alarm rules. 1.2 Functions CES provides the following functions: Automatic Monitoring: Monitoring starts automatically after ECSs or AS groups are created. No manual intervention or additional plug-ins aer required. Issue 13 ( ) 2

5 1 Introduction After obtaining resources, you can view instance monitoring data on the Instance Monitoring page of the CES console within 5 to 10 minutes. During this time the system is trying to obtain and aggregate data. Flexible Alarm Configuration: You can configure alarm rules and thresholds for specific metrics. You can also disable or enable alarm rules as required. When you add alarm rules, you can choose to monitor one metric for multiple instances (if multiple instances contain the same target metric). Thus, allowing you to successfully add monitored objects in batches. Alarm rule parameter values, such as threshold, can be modified at any time. Newly set parameter values will take effect with the start of the next monitoring period. If a monitored instance is not used, you can disable the alarm rule for that instance. If the instance is used again, you can then enable the alarm rule. If the monitored instance is not used or has been deleted, you can manually delete the alarm rule for the instance. Real-time Notification: You can enable the alarm notification function to receive notification text messages and s, or enable CES to send messages to the server. If an alarm is generated due to insufficient data, or an alarm is cleared, CES sends notifications to your registered mobile phone, box. CES sends only one notification for an alarm even if the alarm is active for a long period of time. Following Metrics: On the Dashboard page, you can follow metrics. This function allows you to view metrics of monitored service instances laid out in detailed charts. CES dashboard supports multi-metric comparison. To stop following metrics you need to delete the charts. 1.3 Application Scenarios Routine Management Problem Notification Capacity Adjustment CES provides all-around monitoring for your resources, including CPUs, disk I/O, and network traffic, ensuring end-to-end delivery of your services. If an alarm is generated, the available data is insufficient for requirements, or an alarm is cleared, CES sends notifications to your registered mobile phone or box. After you configure alarm rules for resource-related metrics, you can obtain information about the running status of monitored objects in a timely manner, and scale up resources if receiving notifications indicating resource insufficiency. 1.4 Related Services CES generates alarms that can trigger AS to implement appropriate scaling actions. Issue 13 ( ) 3

6 1 Introduction Alarm rules configured during AS group creation are synchronized to CES. CES then generates alarms and sends those alarms through AS to implement scaling actions. For ECS instances performing similar functions you can create monitoring tasks for specific metrics to centralize monitoring and alarm reporting for those instances. You can directly switch to the CES console from the ECS console to view monitored information about specific ECSs. If an ECS instance stops, becomes faulty, or is deleted, its monitoring data cannot be queried from the CES console. If the instance is restarted or recovers, you can view its data again. One hour after an instance stops or becomes faulty, CES will delete the instance and no longer monitor it. If this happens, you need to manually delete the alarm rules for that instance. CES monitors resources of the following services: ECS, EVS, VPC, ELB, AS, RDS,, DMS, and Workspace. Table 1-2, Table 1-3, Table 1-4, Table 1-5, Table 1-6, Table 1-7, Table 1-8, Table 1-9, and Table 1-10 list monitored metrics of different services. Table 1-2 ECS monitoring metrics Metric Description Formula Remarks CPU Usage Indicates the CPU usage (%) of an ECS. CPU usage of an ECS/Number of CPU cores in the ECS Memory Usage Indicates the memory usage (%) of an ECS. Used memory of an ECS/Total memory of the ECS This metric is unavailable if the image has no vmtools installed. Disk Usage Indicates the disk usage (%) of an ECS. Used capacity of an ECS disk/total capacity of the ECS disk This metric is unavailable if the image has no vmtools installed. Disks Read Rate Indicates the number of bytes read from an ECS per second. Total number of bytes read from an ECS disk/monitoring period byte_out = (rd_bytes - last_rd_bytes) /Time difference Disks Write Rate Indicates the number of bytes written to an ECS per second. Total number of bytes written to an ECS disk/monitoring period Disks Read Requests Indicates the number of read requests sent to an ECS per second. Total number of read requests sent to an ECS disk/monitoring period req_out = (rd_req - last_rd_req)/ti me difference Disks Write Requests Indicates the number of write requests sent to an Total number of write requests sent to an req_in = (wr_req - Issue 13 ( ) 4

7 1 Introduction Metric Description Formula Remarks ECS per second. ECS disk/monitoring period last_wr_req)/ti me difference Inband Incoming Rate Indicates the number of incoming bytes on an ECS per second. Total number of inband incoming bytes on an ECS/Monitoring period Inband Outgoing Rate Indicates the number of outgoing bytes on an ECS per second. Total number of inband outgoing bytes on an ECS/Monitoring period Outband Incoming Rate Indicates the number of incoming bytes on an ECS per second at the virtualization layer. Total number of outband incoming bytes on an ECS/Monitoring period This metric is unavailable if SR-IOV is enabled. Outband Outgoing Rate Indicates the number of outgoing bytes on an ECS per second at the virtualization layer. Total number of outband outgoing bytes on an ECS/Monitoring period This metric is unavailable if SR-IOV is enabled. Failed to check the system status This metric is used to monitor the cloud platform on which ECSs run. The system periodically checks the system status and returns check results using value 0 or 1. 0: The system is running properly. All check items are normal. When the power source of the physical host fails or the hardware/softw are becomes faulty, the check result is 1. 1: The system is not running properly. One or multiple check items are abnormal. Table 1-3 EVS monitoring metrics Metric Definition Monitored Object Formula Disk Read Rate This metric is used to show the number of bytes read from the monitored object per second (bytes/second). EVS disks Total number of bytes read from an EVS disk attached to the server/monitoring period Disk Write This metric is used to show the EVS disks Total number of bytes Issue 13 ( ) 5

8 1 Introduction Metric Definition Monitored Object Rate number of bytes written to the monitored object per second (bytes/second). Formula written to an EVS disk attached to the server/monitoring period Disk Read Requests This metric is used to show the number of read requests sent to the monitored object per second (requests/second). EVS disks Total number of requests for reading data from an EVS disk attached to the server/monitoring period Disk Write Requests This metric is used to show the number of write requests sent to the monitored object per second (requests/second). EVS disks Total number of requests for writing data to an EVS disk attached to the server/monitoring period Table 1-4 VPC monitoring metrics Metric Definition Value Range Monitored Object Upstream bandwidth Specifies the outbound network rate of the monitored object. bit/s Bandwidth or EIP Downstream bandwidth Specifies inbound network rate of the monitored object. bit/s Bandwidth or EIP Upstream Traffic Specifies the outbound network traffic of the monitored object. byte Bandwidth or EIP Downstream Traffic Specifies the inbound network traffic of the monitored object. byte Bandwidth or EIP Table 1-5 ELB monitoring metrics Metric cps Active Connections Inactive Connections New cps Description This metric is used to show the number of concurrent connections processed by the monitored object per second (connections/second). This metric is used to show the number of active connections processed by the monitored object per second (connections/second). This metric is used to show the number of inactive connections processed by the monitored object per second (connections/second). This metric is used to show the number of new connections processed by the monitored object per second Issue 13 ( ) 6

9 1 Introduction Metric Incoming Packets Outgoing Packets Inbound Rate Outbound Rate Abnormal Hosts Normal Hosts Description (connections/second). This metric is used to show the number of incoming packets on the monitored object per second (packets/second). This metric is used to show the number of outgoing packets on the monitored object per second (packets/second). This metric is used to show the number of incoming bytes per second (bytes/second) on the monitored object. This metric is used to show the number of outgoing bytes per second (bytes/second) on the monitored object. This metric is used to show the number of abnormal backend hosts. This metric is used to show the number of normal backend hosts. Table 1-6 AS monitoring metrics Metric Description Monitored Object Formula CPU Usage Indicates the CPU usage (%) of a monitored object. AS group CPU usage of all ECS instances in an AS group/number of CPU cores of all ECS instances in the AS group Memory Usage Indicates the memory usage (%) of a monitored object. AS group Memory usage of all ECS instances in an AS group/total memory size of all ECS instances in the AS group Instance Qty. Specifies the number of available ECSs in a monitored object. AS group Total number of normal ECSs in an AS group Inband Incoming Rate Indicates the number of incoming bytes per second (bytes/second) on the monitored object. AS group (Total incoming bytes of all ECS instances in an AS group/total number of ECS instances in the AS group)/monitoring period Inband Outgoing Rate Indicates the number of outgoing bytes per second (bytes/second) on the monitored object. AS group (Total outgoing bytes of all ECS instances in an AS group/total number of ECS instances in the AS group)/monitoring period Issue 13 ( ) 7

10 1 Introduction Table 1-7 RDS monitored metrics Metric Description Value Range Monitored Object CPU Usage Memory Usage CPU usage (%) of the monitored object. memory usage (%) of the monitored object. 0% to 100% ECS 0% to 100% ECS IOPS number of I/O operations per second on the monitored object. It is measured in counts. counts/s ECS Network Input Throughput Measures incoming traffic in bytes per second. bytes/s ECS Monitored instance type: MySQL, PostgreSQL, and Microsoft SQL Server instances Network Output Throughput Measures outgoing traffic in bytes per second. bytes/s ECS Monitored instance type: MySQL, PostgreSQL, and Microsoft SQL Server instances Total Connections total number of connection attempts to the MySQL server. It is measured in counts. counts Current Active Connections number of current active connections. It is measured in counts. counts QPS number of SQL statement queries (including the storage process) per second. queries/s TPS number of transaction executions (including transaction submitting and rollback) per second. transactions/s Buffer Pool Usage Buffer Pool Hit Rate ratio (%) of dirty data from all data in the InnoDB buffer. ratio (%) of read hits to read requests (Innodb_buffer_pool_reads indicates the number of times that 0% to 100% 0% to 100% Issue 13 ( ) 8

11 1 Introduction Metric Description Value Range Monitored Object disks are read). Buffer Pool Dirty Block Rate ratio (%) of dirty pages from all pages in the buffer pool. 0% to 100% InnoDB Read Throughput average number of read bytes per second for the InnoDB buffer. bytes/s InnoDB Write Throughput number of write bytes per second for the InnoDB buffer. bytes/s InnoDB File Read Frequency average number of times that InnoDB reads files per second. counts/s InnoDB File Write Frequency average number of times that InnoDB writes files per second. counts/s InnoDB Log Write Request Frequency average number of log write requests per second. counts/s InnoDB Log Physical Write Frequency average number of physical writes for log files per second. counts/s InnoDB Log fsync() Write Frequency average number of fsync write requests on log files per second. counts/s Temporary Tables Qty number of temporary tables automatically created on hard disks when MySQL statements are executed. tables Key Buffer Usage Key Buffer Write Hit Rate Key Buffer Read Hit Rate MyISAM key buffer usage (%). key buffer write hit usage (%) of MyISAM. key buffer read hit usage (%) of MyISAM. 0% to 100% 0% to 100% 0% to 100% MyISAM Disk Write Speed average number of times that indexes are written into disks per second. counts/s MyISAM Disk Read Speed average number of times that indexes are read from disks per second. counts/s MyISAM average number of counts/s Issue 13 ( ) 9

12 1 Introduction Metric Description Value Range Monitored Object Buffer Pool Write Speed requests to write indexes into cache per second. MyISAM Buffer Pool Read Speed average number of requests to read indexes from cache per second. counts/s Delete Execute Speed average number of Delete executions per second. queries/s Insert Execute Speed average number of Insert executions per second. queries/s Insert_Select Execute Speed average number of Insert_Select executions per second. queries/s Replace Execute Speed average number of Replace executions per second. queries/s Replace_Selec tion Execute Speed average number of Replace_Selection executions per second. queries/s Select Execute Speed average number of Select executions per second. queries/s Update Execute Speed average number of Update executions per second. queries/s Row Delete Speed average number of rows that are deleted from the InnoDB table per second. rows/s Row Insert Speed average number of rows that are inserted to the InnoDB table per second. rows/s Row Read Speed average number of rows that are read from the InnoDB table per second. rows/s Row Update Speed number of updated rows in the InnoDB table per second. rows/s Disk Usage disk usage (%) of the monitored object. 0% to 100% ECS Transaction Logs Usage disk capacity used by transaction logs. MB Replication Slot Usage disk capacity used by replication slot files. MB Connections number of database connections in use. counts Issue 13 ( ) 10

13 1 Introduction Metric Description Value Range Monitored Object Maximum Used Transaction IDs maximum transaction ID that has been used. counts Transaction Logs Generations size of transaction logs generated per second. MB/s Oldest Replication Slot Lag lagging size of the most lagging replica in terms of WAL data received. MB Replication Lag replication lag delay. ms Total Disk Size total disk size of the monitored object. 100 GB to 2000 GB ECS Disk Usage disk usage of the monitored object. 0 GB to 2000 GB ECS Disk Read Throughput number of bytes read from the disk per second. bytes/s ECS Disk Write Throughput number of bytes write to the disk per second. bytes/s ECS Average Time per Disk Read Average Time per Disk Write average time per disk read operation. average time per disk write operation. > 0s ECS > 0s ECS Average Disk Queue Length number of processes to be written to the monitored object. ECS Number of Connections In Use number of database connections in use. 0 counts Table 1-8 monitored metrics Metric Description Value Range Monitored Object CPU Usage Memory Usage CPU usage (%) of the monitored object. memory usage (%) of the monitored 0% to 100% ECS 0% to 100% ECS Issue 13 ( ) 11

14 1 Introduction Metric Description Value Range Monitored Object object. Network Input Throughput inbound throughput per second (byte/s) on the port. bytes/s ECS Network Output Throughput outbound throughput per second (byte/s) on the port. bytes/s ECS Connected Clients number of connected clients, excluding slave nodes. Client Longest Output List longest output list among all the connections to a client. Client Biggest Input Buf maximum input data length (bytes) among all the connections to a client. bytes/s Blocked Clients number of clients that are suspended by block operations, such as BLPOP, BRPOP, and BRPOPLPUSH operations. Used Memory memory (bytes) that Redis has used. bytes/s Used Memory RSS Measures how much RSS memory (bytes) is used by Redis and is in RAM. It includes all stack and heap memory but does not include the memory that is swapped out. bytes/s Used Memory Peak peak value of the memory bytes/s Issue 13 ( ) 12

15 1 Introduction Metric Description Value Range Monitored Object usage (bytes) since the Redis server starts. Used Memory Lua memory (bytes) that the Lua engine has used. bytes/s Memory Fragmentation Ratio current memory fragmentation ratio. Its value is the same as that of used_memory_rss and used_memory. If the used memory peak value is much greater than the used memory, the reference value of this parameter decreases. Total Connections Received total number of connections that the Redis server has received since it started. Total Commands Processed total number of commands that the Redis server has processed since it started. Instantaneous Ops Per Second number of commands processed per second (ops/s). Total Net Input Bytes total number of bytes that the Redis server has received since it started. bytes/s Total Net Output Bytes total number of bytes that the Redis server has sent since it started. bytes/s Issue 13 ( ) 13

16 1 Introduction Metric Description Value Range Monitored Object Instantaneous Input Kbps instantaneous input traffic (kbit/s). kbit/s Instantaneous Output Kbps instantaneous output traffic (kbit/s). kbit/s Rejected Connections number of connections that have exceeded maxclients and been rejected by the Redis server since it started. Sync Full total number of full synchronizations since the Redis server started. Sync Partial OK total number of incremental synchronizations since the Redis server started. Sync Partial Err total number of failed incremental synchronizations since the Redis server started. Expired Keys total number of keys that have expired since the Redis server started. Evicted Keys number of keys that have been evicted due to insufficient memory since the Redis server started. Keyspace Hits total number of query hits in the master dictionary since the Redis server started. Issue 13 ( ) 14

17 1 Introduction Metric Description Value Range Monitored Object Keyspace Misses total number of query misses in the master dictionary since the Redis server started. PubSub Channels number of Pub/Sub channels. PubSub Patterns number of Pub/Sub patterns. Aof Current Size AOF file size (bytes). Latest Fork usec latest fork time (ms). ms Table 1-9 DMS monitored metrics Metric Description Value Range Monitored Object Queued Messages accumulated number of messages in a queue. DMS queue Message Size (byte) accumulated size of messages in a queue. DMS queue Request Count accumulated number of requests sent to a queue. DMS queue Accumulated Messages accumulated number of retrievable messages in a consumer group. DMS consumer group Consumed Messages accumulated number of messages (including dead letter messages) retrieved by a consumer group. DMS consumer group Skipped Messages accumulated number DMS consumer Issue 13 ( ) 15

18 1 Introduction Metric Description Value Range Monitored Object of messages that have been deleted without being retrieved from a queue due to expiration. group Available Dead Letter Messages accumulated number of dead letter messages retrievable to a consumer group. DMS consumer group Historical Dead Letter Messages accumulated number of dead letter messages that have been generated for a consumer group since the consumer group is created. These dead letter messages include the retrieved dead letter messages, remaining dead letter messages, and expired dead letter messages. DMS consumer group Table 1-10 Workspace monitored metrics Metric Description Value Range Monitored Object CPU Usage Memory Usage Disk Usage CPU usage of the monitored object. Unit: % memory usage of the monitored object. Unit: % disk usage of the monitored object. Unit: % 0% to 100% IaaS 0% to 100% IaaS 0% to 100% IaaS IOPS number of I/O operations per second on the monitored object. It is measured in counts. counts IaaS Network Input Throughput number of incoming bytes per second on the monitored object. The unit is bytes/second. bytes/s IaaS Issue 13 ( ) 16

19 1 Introduction Metric Description Value Range Monitored Object Network Output Throughput number of outgoing bytes per second on the monitored object. The unit is bytes/second. bytes/s IaaS 1.5 User Permissions The public cloud system provides two types of default user permissions: user management and resource management. User management refers to the management of users, user groups, and user group rights. Resource management refers to control operations that performed on cloud service resources. For details about CES user permissions, see Permissions. 1.6 Region A region is a geographical area where the CES service is deployed. Each region comprises one or more AZs and is isolated from other regions. Only AZs in the same region can communicate with one another through an internal network. Public cloud data centers are distributed in many locations worldwide, such as North America, Europe, and Asia. You can use CES in different regions. Provisioning CES in the required region can better suit local users' requirements or comply with local laws and regulations. 1.7 Projects Projects are used to group and isolate OpenStack resources, including computing, storage, and network resources. A project can be a department or a project team. Multiple projects can be created for one account. Issue 13 ( ) 17

20 2 Getting Started 2 Getting Started Adding an Alarm Rule 1. Log in to the management console. 2. Click in the upper left corner and select the desired region and project. 3. Under Management & Deployment, click Cloud Eye. 4. Choose Alarm > Alarm Rule and click Add Alarm Rule. 5. On the Add Alarm Rule page, set parameters as prompted. a. Select a monitored object and configure parameters listed in Table 2-1. Click Next. Table 2-1 Parameters Parameter Description Example Value Service Dimension Object Specifies name of the service for which the alarm rule is configured. Specifies monitored metric dimension of the alarm rule. Specifies instance of the alarm rule. You can specify one or more monitored objects. Elastic Cloud Server ECS b. Select a monitored object and configure parameters listed in Table 2-2. Click Next. Table 2-2 Parameters Parameter Description Example Value Source You can select and import one from the template or create an alarm rule. If you select xx, configure parameters based on Table 2-3. Import from template Template Specifies the template to be imported. Send Notification Specifies whether to notify users by sending s or send HTTP or HTTPS to the Yes Issue 13 ( ) 18

21 2 Getting Started Parameter Description Example Value servers. Select Yes (recommended). Select No. Topic Name Trigger Condition Specifies the name of the topic to which the alarm notification is sent. If you select Yes for Send Notification, you need to select a topic name or create a topic. For details, see step 5 Specifies the condition for triggering an alarm. You can select one or more from the following: Generated alarm, Cleared alarm, and Insufficient data. Table 2-3 Parameters Parameter Description Example Value Metric Threshold Occurrences Monitoring Interval For example, CPU Usage This metric is used to show the CPU usage (%) of the monitored object. Memory Usage This metric is used to show the memory usage (%) of the monitored object. Specifies the condition for generating the alarm. The threshold consists of rollup methods (Raw data, Max., Min., Avg., Sum., and Variance), identification conditions (>,, <,, and =), and critical value. For example, an average value greater than 80 is a condition for generating an alarm. Specifies the number of sampling points when an alarm is triggered. For example, if Occurrences is set to n, the sampling point of the alarm rule is the sampling points in n consecutive monitoring intervals. Only all the sampling points meet the threshold configured for the alarm rule, will the alarm rule status be refreshed as the Alarm status. Raw data uses a default 5-minute monitoring period. Specifies the interval at which the alarm status is updated based on the alarm rule minutes Issue 13 ( ) 19

22 2 Getting Started Parameter Description Example Value Send Notification Topic Name Trigger Condition Specifies whether to notify users by sending s or send HTTP or HTTPS to the servers. Select Yes (recommended). Select No. Specifies the name of the topic to which the alarm notification is sent. If you select Yes for Send Notification, you need to select a topic name or create a topic. For details, see step 5 Specifies the condition for triggering an alarm. You can select one or more from the following: Generated alarm, Cleared alarm, and Insufficient data. Yes c. On the page shown in Table 2-4, set the parameters as prompted. Click Add. The alarm rule is added. Table 2-4 Parameters Parameter Description Example Value Name Description Specifies name of the alarm rule. The system generates a name randomly but you can change it. Provides supplementary information about the alarm rule. This parameter is optional. alarm-b6al 6. Create a topic. On the Add Alarm Rule page, click Create Topic to switch to the management console of Simple Message Notification (SMN). For details, see section "Creating a Topic" in the Simple Message Notification. 7. After creating the topic, click on the right of Create Topic to return to the Add Alarm Rule page, and select the topic created in step 5 8. Click OK. Issue 13 ( ) 20

23 3 Operation Guide 3 Operation Guide 3.1 Dashboard Viewing Alarm Rules 1. Log in to the management console. 2. Click in the upper left corner and select the desired region and project. 3. Under Management & Deployment, click Cloud Eye. 4. On the Dashboard page, click View Alarm Rule. On the displayed Alarm Rule page, view detailed alarm rule information in the alarm rule list. Viewing Monitored Metric Statistics 1. Log in to the management console. 2. Click in the upper left corner and select the desired region and project. 3. Under Management & Deployment, click Cloud Eye. 4. If you have signed up for one or more of the following services: ECS, EVS, VPC, ELB, AS, API Gateway,, DWS, ULB, DMS,, Workspace, or RDS, you can view any metric quantity associated with a service in the Metric Statistics area on the Dashboard page without installing other plug-ins. On the Dashboard page, you can switch to the Instance Monitoring page by clicking an instance name. Creating a Monitoring Panel On the Dashboard page, Metric Quantity associated with a service is the total number of metrics summarized over all instances for that service. For example, if you have bought 2 EVS instances and each EVS instance has 4 metrics, then the total EVS Metric Quantity on the Dashboard page is 8. On the Instance Monitoring page, Metric Quantity associated with an instance is the number of metrics available for this instance. Different ECSs may have different numbers of monitored metrics. For details, see Table Log in to the management console. 2. Under Management & Deployment, click Cloud Eye. Issue 13 ( ) 21

24 3 Operation Guide 3. In the navigation pane on the left, choose Dashboard > Monitoring Panel and click Create Monitoring Panel. The Create Monitoring Panel page is displayed. 4. Configure Name. Name indicates the monitoring panel name, which can contain letters, digits, hyphens (-), and underscores (_), and cannot exceed 128 characters. Customizing Monitored Metrics If you add visuals for the first time, you need to create a monitoring panel, which can hold a maximum of 24 visuals. If you add more than 24 visuals to a monitoring panel, you need to create a second monitoring panel. A maximum of up two monitoring panels can be created currently. You can rename or delete the monitoring panel as needed. 1. Log in to the management console. 2. Click in the upper left corner and select the desired region and project. 3. Under Management & Deployment, click Cloud Eye. 4. (Optional) Create a monitoring panel. For details, see Creating a Monitoring Panel. 5. In the navigation pane on the left, choose Dashboard > Monitoring Panel and click. The Add Monitoring Metric window is displayed. 6. On the displayed page, configure parameters as prompted, as shown in Table 3-1. Multi-metric display is supported. A maximum of up to 5 monitored metrics are currently supported. Table 3-1 Parameters Parameter Description Example Value Title Specifies title of the custom metric. The name can contain letters, digits, underscores (_), and hyphens (-). Service Specifies service name of the monitored metric. Dimension Specifies monitored metric dimension. Monitored Object Specifies monitored object of the metric. Metric Specifies the monitored metric name. 7. Click OK. After adding a monitored metric, you can view the corresponding instance information in the Monitoring Panel area. Click to enlarge the window for viewing detailed metric data. Issue 13 ( ) 22

25 3 Operation Guide Querying Monitored Metrics In the Monitoring Panel area, click metrics. to view detailed data and trends of multiple On the displayed page, you can select a time range from those provided on the page or manually specify a time range for instance monitoring. The service allows you to select a fixed time range or customize the time range. The fixed time range can be Last 1 hour, Last 3 hours, Last 12 hours, Last 24 hours, Last 7 days, or Last 30 days. By default, monitoring data of Last 3 hours is displayed. If Last 1 hour is selected, raw metric data is displayed by default. When you select Last 3 hours, Last 12 hours, Last 24 hours, Last 7 days, or Last 30 days, the aggregated metric data is displayed by default. Custom time ranges can be any time within the last week. On the displayed page, results of monitored metrics are displayed in a list by default. You can click a monitored metric to hide its trend, or click the monitored metric again to display its trend. Configuring Monitored Metrics The metric trend graph is automatically refreshed every 1 minute. In the Monitoring Panel area, click. On the displayed page, you can modify the title of a monitored metric, delete the original metric, or select a new metric to be viewed. Deleting Monitored Metrics In Monitoring Panel, click and click OK. Then you can delete the custom metric. 3.2 Instance Monitoring Exporting Monitoring Data On the Instance Monitoring page, you can view historical performance curves of various service instances after you have enabled one or more of the following services: ECS, EVS, VPC, ELB, AS, DMS,, Workspace, and RDS. You do not need to install additional plug-ins because CES automatically detects and monitors active instances. 1. Log in to the management console. 2. Click in the upper left corner and select the desired region and project. 3. Under Management & Deployment, click Cloud Eye. 4. Under Instance Monitoring, select a service instance. On the displayed page, click Export Monitoring Data. 5. On the displayed Export Monitoring Data page, set parameters as listed in Table 3-2. Issue 13 ( ) 23

26 3 Operation Guide Table 3-2 Parameters Parameter Description Example Value Service Specifies service name of the metric. Elastic Cloud Server Dimension Specifies monitored metric dimension. ECS Monitored Object Specifies monitored object of the metric. Metric Specifies the monitored metric name. Outband Outcoming Rate 6. Click Export. If the lines and columns of exported data file exceed the Excel threshold, you are advised to open it as text. Viewing Monitoring Graphs 1. Log in to the management console. 2. Click in the upper left corner and select the desired region and project. 3. Under Management & Deployment, click Cloud Eye. 4. Under Instance Monitoring, select a service instance. In the Operation column, click View Monitoring Graph. 5. On the Monitoring graph page, graphs of raw data collected in Last 1 hour, Last 3 hours, and Last 12 hours are displayed. In the right corner of the monitoring graph of raw metric data, Max and Min values of the target metric are displayed. By default, nine monitoring graphs are displayed on one page. If the number of monitored metrics of a service instance is more than nine, you can click Load more to view more monitoring graphs. 6. In the upper right corner of the monitoring graph, click to enlarge the graph for viewing detailed data. 7. On the displayed page, select a time range from those provided on the page or manually specify a time range for instance monitoring. The service allows you to select a fixed time range or customize the time range. The fixed time range can be Last 1 hour, Last 3 hours, Last 12 hours, Last 24 hours, Last 7 days, or Last 30 days. If Last 1 hour, Last 3 hours, Last 12 hours, or Last 24 hours is selected, raw metric data is displayed by default. If Last 7 days, or Last 30 days is selected, aggregated metric data is displayed by default. Custom time ranges can be any time within the last six months. 8. On the page of graph details, click Setting. Select Enable rollup. Set Period and Statistic. Issue 13 ( ) 24

27 3 Operation Guide Enable rollup dictates what type of metric data is displayed. If Enable rollup is selected, aggregated metric data is displayed. If Enable rollup is deselected, raw metric data is displayed. Period indicates the time range during which raw sample data is collected. The value can be 5 minutes, 20 minutes, 1 hour, 4 hours, or 1 day. The Period drop-down list provides several recommended values based on the monitoring period you have configured. Statistic indicates the aggregation method to be used, including Max., Min., Avg., Sum., and Variance. 3.3 Alarm Adding an Alarm Rule 1. Log in to the management console. 2. Click in the upper left corner and select the desired region and project. 3. Under Management & Deployment, click Cloud Eye. 4. Choose Alarm > Alarm Rule and click Add Alarm Rule. 5. On the Add Alarm Rule page, set parameters as prompted. a. Select a monitored object and configure parameters listed in Table 3-3. Click Next. Table 3-3 Parameters Parameter Description Example Value Service Dimension Object Specifies name of the service for which the alarm rule is configured. Specifies monitored metric dimension of the alarm rule. Specifies instance of the alarm rule. You can specify one or more monitored objects. Elastic Cloud Server ECS b. Select a monitored object and configure parameters listed in Table 3-4. Click Next. Table 3-4 Parameters Parameter Description Example Value Source You can select and import one from the template or create an alarm rule. If you select xx, configure parameters based on Table 3-5. Import from template Template Specifies the template to be imported. Send Notification Specifies whether to notify users by sending s or send HTTP or HTTPS to the Yes Issue 13 ( ) 25

28 3 Operation Guide Parameter Description Example Value servers. Select Yes (recommended). Select No. Topic Name Trigger Condition Specifies the name of the topic to which the alarm notification is sent. If you select Yes for Send Notification, you need to select a topic name or create a topic. For details, see step 5 Specifies the condition for triggering an alarm. You can select one or more from the following: Generated alarm, Cleared alarm, and Insufficient data. Table 3-5 Parameters Parameter Description Example Value Metric Threshold Occurrences Monitoring Interval For example, CPU Usage This metric is used to show the CPU usage (%) of the monitored object. Memory Usage This metric is used to show the memory usage (%) of the monitored object. Specifies the condition for generating the alarm. The threshold consists of rollup methods (Raw data, Max., Min., Avg., Sum., and Variance), identification conditions (>,, <,, and =), and critical value. For example, an average value greater than 80 is a condition for generating an alarm. Specifies the number of sampling points when an alarm is triggered. For example, if Occurrences is set to n, the sampling point of the alarm rule is the sampling points in n consecutive monitoring intervals. Only all the sampling points meet the threshold configured for the alarm rule, will the alarm rule status be refreshed as the Alarm status. Raw data uses a default 5-minute monitoring period. Specifies the interval at which the alarm status is updated based on the alarm rule minutes Issue 13 ( ) 26

29 3 Operation Guide Parameter Description Example Value Send Notification Topic Name Trigger Condition Specifies whether to notify users by sending s or send HTTP or HTTPS to the servers. Select Yes (recommended). Select No. Specifies the name of the topic to which the alarm notification is sent. If you select Yes for Send Notification, you need to select a topic name or create a topic. For details, see step 5 Specifies the condition for triggering an alarm. You can select one or more from the following: Generated alarm, Cleared alarm, and Insufficient data. Yes c. On the page shown in Table 3-6, set the parameters as prompted. Click Add. The alarm rule is added. Table 3-6 Parameters Parameter Description Example Value Name Description Specifies name of the alarm rule. The system generates a name randomly but you can change it. Provides supplementary information about the alarm rule. This parameter is optional. alarm-b6al Alarm Template 6. Create a topic. On the Add Alarm Rule page, click Create Topic to switch to the management console of Simple Message Notification (SMN). For details, see section "Creating a Topic" in the Simple Message Notification. 7. After creating the topic, click on the right of Create Topic to return to the Add Alarm Rule page, and select the topic created in step 5 8. Click OK. When you enter into the CES Dashboard page for the first time, dialog box Alarm Template Now Available is prompted. If you click Try It Now, the system switches to the Alarm Template page. The alarm template is a set of service-based alarm rules recommended by the system. You can use the preconfigured alarm templates to quickly create alarm rules for cloud resources. Issue 13 ( ) 27

30 3 Operation Guide Disabling an Alarm Rule Enabling an Alarm Rule Modifying an Alarm Rule If this is not the first time that you log in to CES, perform the following steps to view the alarm rule template. 1. Log in to the management console. 2. Click in the upper left corner and select the desired region and project. 3. Under Management & Deployment, click Cloud Eye. 4. In the navigation tree on the left, click Alarm and Alarm Template, and then click Alarm Template. On the Alarm Rule page, locate the row that contains the target alarm rule, click Disable in the Operation column, and click OK on the Disable page displayed. If you want to delete multiple alarm rules, on the Alarm Rule page, select multiple alarm rules, click Disable under Add Alarm Rule, and click OK on the Disable page displayed. On the Alarm Rule page, locate the row that contains the target alarm rule, click Enable in the Operation column, and click OK on the Enable page displayed. If you want to enable multiple alarm rules, on the Alarm Rule page, select multiple alarm rules, click Enable under Add Alarm Rule, and click OK on the Enable page displayed. Alarm rules are enabled by default after they are added. 1. On the Alarm Rule page, click the name of the target alarm rule. On the Basic Info page, click Modify in the upper right corner. To modify the target alarm rule, you can also click Modify in the Operation column on the Alarm Rule page. 2. In the Modify Alarm Rule dialog box, modify parameters of the alarm rule, as listed in Table 3-7. Table 3-7 Parameters Parameter Description Example Value Name Description Service Specifies alarm rule name. The system generates a name randomly but you can change it. Provides supplementary information about the alarm rule. This parameter is optional. Specifies name of the service for which the alarm rule is configured. alarm-b6al Elastic Cloud Server Dimension Specifies monitored metric dimension of the alarm rule. ECS Issue 13 ( ) 28

31 3 Operation Guide Parameter Description Example Value Monitored Object Metric Threshold Occurrences Monitoring Interval Send Notification Specifies instance of the alarm rule. You can specify one or more monitored objects. For example, CPU usage This metric is used to show the CPU usage (%) of the monitored object. Memory usage This metric is used to show the memory usage (%) of the monitored object. Specifies condition for generating an alarm. The threshold consists of three parts: a data type (Raw data, Max., Min., Avg., Sum., and Variance), an identification condition (>,, <,, and =), and a critical value. For example, an average value greater than 80 is a condition for generating an alarm. Specifies the number of sampling points when an alarm is triggered. For example, if Occurrences is set to n, the sampling point of the alarm rule is the sampling points in n consecutive monitoring intervals. Only when all sampling points meet the threshold configured for the alarm rule, will the alarm rule status be refreshed to Alarm. Raw data uses a default 5-minute monitoring interval. Specifies the interval at which the alarm status is updated based on the alarm rule. Specifies whether to notify users by sending s or short messages minutes 3. Click OK. Deleting an Alarm Rule On the Alarm Rule page, locate the row that contains the target alarm rule, click Delete in the Operation column, and click OK on the displayed Delete page. If you want to delete multiple alarm rules, on the Alarm Rule page, select multiple alarm rules, click Disable under Add Alarm Rule, and click OK on the Delete page displayed. Issue 13 ( ) 29

32 4 FAQs 4 FAQs 4.1 What Is Cloud Eye? Cloud Eye (CES) is an open monitoring platform that provides monitoring, alarm reporting, and alarm notifications for your resources. CES can monitor metrics of the following services: Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Virtual Private Cloud (VPC), Relational Service (RDS), Elastic Load Balance (ELB), Auto Scaling (AS), Distributed Message Service (DMS), Distributed Cache Service (), and Workspace. You can add alarm rules and configure alarm notification policies to learn the running status and performance of service instances in a timely manner. Table 4-1 describes the functions provided by CES. Table 4-1 CES functions Function Dashboard Description Displays the number of metrics for each service monitored by CES. You can add or delete monitored metrics. You can choose from the following service metrics. ECS: CPU Usage, Disk Read Rate, Disk Read Requests, Disk Usage, Disks Write Rate, Disks Write Requests, Memory Usage, Inband Incoming Rate, Inband Outgoing Rate, Outband Incoming Rate, System Status Check Failed, and Outband Outgoing Rate EVS: Disks Read Rate, Disks Write Rate, Disks Read Requests, and Disks Write Requests AS: CPU Usage, Memory Usage, Instance Qty., Inbound Rate, and Outbound Rate ELB: cps, Active Connections, Inactive Connections, New cps, Inbound Packets, Outbound Packets, Inbound Rate, Outbound Rate, Abnormal Hosts, and Normal Hosts VPC: Upstream Bandwidth, Downstream Bandwidth, Upstream Traffic, and Downstream Traffic DMS: Accumulated Messages, Consumed Messages, Skipped Messages, Queued Messages, Message Size (byte), Available Dead Letter Messages, Historical Dead Letter Messages, and Request Count : CPU Usage, Memory Usage, Network Input Throughput, Network Output Throughput, Connected Clients, Client Longest Output List, Client Biggest Input Buf, Blocked Clients, Used Memory, Used Memory RSS, Used Memory Peak, Used Memory Lua, Memory Fragmentation Ratio, Total Connections Received, Total Commands Processed, Instantaneous Ops Per Second, Total Net Input Bytes, Total Net Output Bytes, Instantaneous Input Kbps, Issue 13 ( ) 30