Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- My Dashboards
- Resource Groups
- Using the Alarm Function
-
Server Monitoring
- Introduction to Server Monitoring
- Agent Installation and Configuration
- Agent Features per Version
- Installing and Configuring the Agent on a Linux ECS or BMS
- Installing and Configuring the Agent on a Windows ECS
- Installing the Agents in Batches on Linux ECSs
- Managing the Agent
- Installing the GPU Metrics Collection Plug-in (Linux)
- Installing the Direct Connect Metric Collection Plug-ins
- Process Monitoring
- Viewing Server Monitoring Metrics
- Creating an Alarm Rule to Monitor a Server
- Custom Monitoring
- Event Monitoring
- Task Center
- Data Dump
- Cloud Service Monitoring
- Permissions Management
- Quota Adjustment
- Services Interconnected with Cloud Eye
- Change History
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
API V1
- API Version Management
- Metrics
-
Alarm Rules
- Querying Alarm Rules
- Querying Details of an Alarm Rule
- Enabling or Disabling an Alarm Rule
- Deleting an Alarm Rule
- Creating an Alarm Rule
- Creating a Custom Alarm Template
- Deleting a Custom Alarm Template
- Querying the Alarm History of an Alarm Rule
- Querying Custom Alarm Templates
- Updating a Custom Alarm Template
- Modifying an Alarm Rule
- Monitoring Data
- Quotas
- Resource Groups
- Event Monitoring
-
API V2
- Alarm Rules
- Resources in an Alarm Rule
- Alarm Policies
- Alarm Notifications
- Alarm Records
- Alarm Templates
- Alarm Rules Associated with an Alarm Template
- Resource Groups
- Resources in a Resource Group
-
One-Click Monitoring
- Enabling One-Click Monitoring
- Querying Services and Resources That Support One-Click Monitoring
- Querying Alarm Rules of One Service in One-Click Monitoring
- Batch Enabling or Disabling Alarm Rules of One Service in One-Click Monitoring
- Batch Disabling One-Click Motoring
- Batch Modifying Alarm Notifications in Alarm Rules for One Service That Has One-Click Monitoring Enabled
- Batch Enabling or Disabling Alarm Policies in Alarm Rules for One Service That Has One-Click Monitoring Enabled
-
Alarm Notification Masking
- Creating Alarm Notification Masking Rules in Batches
- Modifying the Masking Time of Alarm Notification Masking Rules in Batches
- Modifying an Alarm Notification Masking Rule
- Deleting Alarm Notification Masking Rules in Batches
- Querying Alarm Notification Masking Rules
- Querying Resources for Which Alarm Notifications Have Been Masked
- Dashboards
- Graphs
- Resource Tags
- Metric Management
- API V3
-
Permissions Policies and Supported Actions
- Introduction
- Supported Actions of the API Version Management APIs
- Supported Actions of the Metric Management API
- Supported Actions of the Alarm Rule Management APIs
- Supported Actions of the Monitoring Data Management APIs
- Supported Actions of the Quota Management API
- Supported Actions of the Event Monitoring API
- Common Parameters
- Appendix
- Change History
- SDK Reference
-
FAQs
- General Consulting
-
Server Monitoring
- How Does the Cloud Eye Agent Obtain a Temporary AK/SK by Authorization?
- How Can I Quickly Restore the Agent Configuration?
- How Can I Ensure that a Newly Purchased ECS Comes with the OS Monitoring Function?
- Why Is a BMS with the Agent Installed Displayed in the ECS List on the Server Monitoring Page?
- What OSs Does the Agent Support?
- What Statuses Does the Agent Have?
- What Should I Do If the Monitoring Period Is Interrupted or the Agent Status Keeps Changes?
- What Should I Do If the Service Port Is Used by the Agent?
- What Should I Do If the Agent Status Is Faulty?
-
Alarm Notifications or False Alarms
- What Is an Alarm Notification? How Many Types of Alarm Notifications Are There? How Can I Configure an Alarm Notification?
- What Alarm Status Does Cloud Eye Support?
- What Alarm Severities Does Cloud Eye Support?
- When Will an "Insufficient data" Alarm Be Triggered?
- How Do I Monitor and View the Disk Usage?
- How Can I Change the Phone Number and Email Address for Receiving Alarm Notifications?
- How Can a User Account Receive Alarm Notifications?
- Why Did I Receive a Bandwidth Overflow Notification While There Being No Bandwidth Overflow Record in the Monitoring Data?
-
Monitored Data Exceptions
- Why Is the Monitoring Data Not Displayed on the Cloud Eye Console?
- Why I Cannot See the Monitoring Data on the Cloud Eye Console After Purchasing Cloud Service Resources?
- Why Doesn't the Cloud Eye Console Display the OS Monitoring Data or Why Isn't the Data Displayed Immediately After the Agent Is Installed and Configured on an ECS?
- Why Is Basic Monitoring Data Inconsistent with Data Monitored by the OS?
- Why Are the Network Traffic Metric Values in Cloud Eye Different from Those Detected in ECS?
- Why Is the Metric Collection Point Lost During Certain Periods of Time?
- Why Are the Four Metrics Memory Usage, Disk Usage, Inband Incoming Rate, and Inband Outgoing Rate Not Displayed for an ECS?
- What Are the Impacts on ECS Metrics If UVP VMTools Is Not Installed on ECSs?
-
User Permissions
- What Should I Do If the IAM Account Permissions Are Abnormal?
- What Can I Do If the System Displays a Message Indicating Insufficient Permissions When I Access Cloud Eye?
- What Can I Do If the System Displays a Message Indicating Insufficient Permissions When I Click Configure on the Server Monitoring Page?
- Videos
Modifying the DNS Server Address and Adding Security Group Rules (Linux)
Scenarios
This topic describes how to add the DNS server address and security group rules to a Linux ECS or BMS to ensure successful downloading of the Agent installation package and successful monitoring data collection. This section takes an ECS as an example. The operations for BMSs are similar.
You can modify the DNS server address of an ECS via command lines or the management console.
DNS and security group configuration are intended for the primary NIC.
Modifying the DNS Server Address (Command Lines)
The following describes how to add the DNS server address to the resolv.conf file using command lines.
To use the management console, see Modifying the DNS Server Address (Management Console).
- Log in to an ECS as user root.
- Run the vi /etc/resolv.conf command to open the file.
- Add the DNS server address, for example, nameserver 100.125.1.250 and nameserver 100.125.21.250 to the file. Enter :wq and press Enter to save the change.
Figure 1 Adding the DNS server address (Linux)
NOTE:
The nameserver value varies depending on the region. For details, see What Are the Private DNS Servers Provided by the Huawei Cloud?
Modifying the DNS Server Address (Management Console)
The following describes how to modify the DNS server address of an ECS on the management console. This section takes an ECS as an example. The operations for BMSs are similar.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner. Under Compute, select Elastic Cloud Server.
On the ECS console, click the name of the ECS to view its details.
- On the displayed Summary tab page, click the VPC name.
The Virtual Private Cloud page is displayed.
- Click the name of the VPC.
- In the Networking Components area, click the number following Subnets.
The Subnets page is displayed.
- In the subnet list, click the name of the subnet.
- In the Gateway and DNS Information area, click
following DNS Server Address.
- Click OK.
NOTE:
The new DNS server address is applied after the ECS or BMS is restarted.
Modifying the ECS Security Group Rules (Management Console)
The following describes how to modify security group rules for an ECS on the management console. The operations for BMSs are similar.
- On the ECS details page, click the Security Groups tab.
The security group list is displayed.
- Click the security group name.
- Click Modify Security Group Rule.
The security group details page is displayed.
NOTE:
Procedure for BMS:
- Click the security group ID on the upper left.
- Click Manage Rule in the Operation column of the security group.
- Click the Outbound Rules tab, and click Add Rule.
- Add rules based on Table 1.
Table 1 Security group rules Protocol
Port
Type
Destination
Description
TCP
80
IPv4
100.125.0.0/16
Used to download the Agent installation package from an OBS bucket to an ECS or BMS and obtain the ECS or BMS metadata and authentication information.
TCP and UDP
53
IPv4
100.125.0.0/16
Used by DNS to resolve domain names, for example, resolve the OBS domain name when you are downloading the Agent installation package, and resolve the Cloud Eye endpoint when the Agent is sending monitoring data to Cloud Eye.
TCP
443
IPv4
100.125.0.0/16
Used to collect monitoring data and send the data to Cloud Eye.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.