Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.
- What's New
- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
- Edge Computing with IEF
- Service Instances
-
User Guide (Professional)
- Node Management
-
End Device Management
- End Devices and Device Twins
- Device Templates
- End Devices
- Binding an End Device to an Edge Node
- Device Twin Working Principles
- Migrating Device Data to the Cloud
- Performing Security Authentication Using Certificate
-
MQTT Topics
- Device Twin Update
- Device Twin Delta
- Device Member Update
- Device Property Update
- Device Member Acquisition
- Device Member Acquisition Result
- Device Twin Acquisition
- Device Twin Acquisition Result
- Device Twin Modification
- Device Twin Modification Result
- Encryption Data Request
- Encryption Data Acquisition
- Alarm Reporting
- Alarm Clearance
- Custom Topics
- Containerized Application Management
- Edge-Cloud Messages
- Batch Management
- Auditing
- Permissions Management
-
User Guide (Platinum)
- Node Management
-
End Device Management
- End Devices and Device Twins
- Device Templates
- End Devices
- Binding an End Device to an Edge Node
- Device Twin Working Principles
- Migrating Device Data to the Cloud
- Performing Security Authentication Using Certificate
-
MQTT Topics
- Device Twin Update
- Device Twin Delta
- Device Member Update
- Device Property Update
- Device Member Acquisition
- Device Member Acquisition Result
- Device Twin Acquisition
- Device Twin Acquisition Result
- Device Twin Modification
- Device Twin Modification Result
- Encryption Data Request
- Encryption Data Acquisition
- Alarm Reporting
- Alarm Clearance
- Custom Topics
- Containerized Application Management
- Application Mesh
- Edge-Cloud Messages
- Batch Management
- Auditing
- Permissions Management
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
-
Edge Node Management
- Registering an Edge Node
- Updating an Edge Node
- Querying Details About an Edge Node
- Querying a List of Edge Nodes
- Deleting an Edge Node
- Starting or Stopping an Edge Node
- Updating End Devices for an Edge Node
- Querying Node Certificates
- Creating a Node Certificate
- Deleting a Node Certificate
- Performing an Edge Node Upgrade Check
- Upgrading Edge Nodes
- End Device Management
- End Device Template Management
-
Application Template Management
- Creating an Application Template
- Updating an Application Template
- Querying Details About an Application Template
- Querying a List of Application Templates
- Deleting an Application Template
- Creating an Application Template Version
- Updating an Application Template Version
- Querying Details About an Application Template Version
- Querying a List of Application Template Versions
- Deleting an Application Version
- Deployment Management
- Tag Management
- ConfigMap Management
- Secret Management
- Endpoint Management
- Rule Management
- System Subscription Event Management
- Batch Node Management
- Batch Job Management
- Quota Management
- Service Management
-
Edge Node Management
- Data Structure
- Permissions Policies and Supported Actions
- Appendix
- Change History
- SDK Reference
-
FAQs
-
Edge Node FAQs
- What Do I Do If an Edge Node Is Faulty?
- What Are the Fault Scenarios of Edge Nodes?
- What Do I Do If Edge Node Management Fails?
- How Do I Obtain the Latest Device Properties After Device Properties Are Updated?
- What Operations Can I Perform After a Device Is Associated with a Node?
- Does an Edge Node Support Multiple GPUs?
- Can I Change the GPU on a Running Edge Node?
- How Is Edge Environment Security Protected?
- Why Cannot I View Monitoring Data on an Edge Node?
- How Can I Restore a Deleted Edge Node?
- What Is the Impact of IP Address Changing on an Edge Node?
- What Do I Do If the NTP Configuration Cannot Be Modified?
- How Do I Synchronize Time with the NTP Server?
- How Do I Obtain the IP Addresses of IEF Cloud Services?
- What Do I Do If the Edge Node Space Is Insufficient?
- How Do I Set Docker Cgroup Driver After Installing Docker on an Edge Node?
-
Edge Application FAQs
- What Do I Do If an Application Fails to Be Delivered to an Edge Node?
- What Do I Do If a Containerized Application Fails to Be Started on an Edge Node?
- What Do I Do If a Containerized Application Fails to Be Upgraded?
- What Do I Do If a Container Image Fails to Be Pulled?
- Why Cannot I View Application Logs and System Logs?
- How Do Applications Schedule GPU Resources?
- How Do I Control the Disk Space Occupied by a Container Engine?
- What Do I Do If a Containerized Application Cannot Access External IP Addresses
- What Do I Do If the Ascend AI Accelerator Card (NPU) Is Abnormal?
-
Edge-Cloud Message FAQs
- What Is Route Management?
- What Is a Message Endpoint in Route Management?
- What Is a Route?
- Why Does a Route Fail to Be Created?
- What Can I Do If a Message Fails to Be Forwarded over a Route?
- What Is the Impact of Disabling a Route?
- What Can I Do If SystemEventBus (MQTT Broker) of an Edge Node Fails to Be Connected?
- Network Management FAQs
- Basic Concept FAQs
-
Others
- Region and AZ
- What Are the Specifications of Edge Nodes Supported by IEF?
- What Are the Differences Between Device Properties and Device Twins?
- What Programming Language Is Required for IEF Development?
- Do I Need to Prepare Edge Nodes by Myself?
- Can I Still Use the Previously Delivered Applications After My Account Is in Arrears?
- What Are the Differences Between IEF and IoT Edge?
- What Do I Do If an Agency Fails to Be Automatically Created?
- How Can I Deal With Insufficient Permissions?
- How Will the Multi-AZ Reconstruction of SWR Application Container Image Data Affect IEF?
-
Edge Node FAQs
-
Edgectl User Guide
- Overview
- Installing edgectl
- Example: Using edgectl to Run Commands
-
edgectl Commands
- Querying the edgectl Version
- Managing the Product Lifecycle
-
Checking an Item
- Checking the Hardware Architecture
- Checking the CPU
- Checking the Memory
- Checking Hard Disks
- Checking the Domain Name Resolution Function
- Checking Docker
- Checking Network Connectivity
- Checking the Installation Status of the IEF Software
- Checking the Running Status of the IEF Software
- Checking GPUs
- Checking NPUs
- Checking Processes
-
Error Codes
- Error Code Overview
- Common Errors
- Permission Errors
-
OS Errors
- ERROR3001 Failed to obtain the hardware architecture
- ERROR3002 Unsupported hardware architecture
- ERROR3101 Failed to obtain the CPU information of the node
- ERROR3102 Failed to obtain the real-time CPU status of the node
- ERROR3103 Insufficient node CPU
- ERROR3201 Failed to obtain the memory information of the node
- ERROR3202 Insufficient node memory
- ERROR3301 Failed to obtain the disk information of the node
- ERROR3302 Insufficient disk space on the node
- ERROR3401 Failed to resolve the domain name
- ERROR3501 Failed to check the network
- ERROR3601 Failed to obtain the process information of the node
- ERROR3602 Failed to obtain the total number of processes on the node
- ERROR3603 Number of remaining processes on the node is insufficient
-
IEF Software Errors
- ERROR5001 Incomplete IEF software installation
- ERROR5002 IEF software is not completely running
- ERROR5003 Failed to read the IEF software configuration file
- ERROR5004 Docker is not enabled for the IEF software
- ERROR5005 Failed to start the IEF software
- ERROR5006 Failed to stop the IEF software
- ERROR5101 No application data found
- ERROR5102 No status data of the application found
- ERROR5103 Container is not started
- ERROR5104 Container exits abnormally
- ERROR5105 Failed to pull the container image
- ERROR5106 Container exits
- Third-Party Dependency Errors
- Data Collection Errors
- Internal Errors
- Videos
- General Reference
Copied.
Logs, Monitoring, and Alarms
Log Description
Enabling logging for an edge node on the IEF console will upload the system and application logs of the edge node to Application Operations Management (AOM).
- System Logs: logs generated by the IEF software (such as edge-core, edge-logger, and edge-monitor) installed on edge nodes.
- Application Logs: logs generated by applications deployed on edge nodes.
- Edge nodes will upload logs in the /var/IEF/app/log directory to AOM through IEF. You can mount the /var/IEF/app/log/{appName} directory into the container when creating an application. For details, see hostPath: used for mounting a directory of the host into the container. You can view logs on AOM by {appName}.
- Edge nodes will also upload container logs in {{DOCKER_ROOT_DIR}}/containers/{containerID}/{containerID}-json.log to AOM. You can run the docker info command to query the value of DOCKER_ROOT_DIR. containerID indicates the container ID.
Viewing Logs on AOM
- Log in to the AOM console.
- In the navigation pane, choose Log > Log Files, and click the Component tab.
- On the displayed page, select cluster ief_global and namespace default.
Figure 1 Selecting a cluster and a namespace
- Search for logs by application name, and click View in the row where the log file resides to view detailed logs.
Viewing Node Monitoring Information on AOM
You can view the node monitoring information on AOM.
- Log in to the AOM console.
- Click the name of the node whose monitoring information is to be viewed.
Figure 2 Selecting a monitored node
- On the View Monitor Graphs tab page, view the resource usage of the node, such as the CPU usage and memory usage.
Figure 3 Viewing monitoring information
Viewing Container Monitoring Information on AOM
You can view the monitoring information about the containerized applications deployed on edge nodes on AOM.
- Log in to the AOM console.
- Select the workload whose monitoring information is to be viewed.
Figure 4 Selecting a workload
- On the View Monitor Graphs tab page, view the monitoring metrics of the container, such as the CPU usage and memory usage.
Figure 5 Viewing monitoring information
Alarms Preset on IEF
IEF comes with seven types of alarms preconfigured for each edge node. These alarms will be automatically reported to AOM.
Alarm Name |
Trigger |
Clearance Condition |
Severity |
---|---|---|---|
Container Engine Is Abnormal |
Docker has been enabled on an edge node, and the Docker information fails to be queried. |
Docker is running properly, and EdgeCore can obtain the Docker information. |
Critical |
Application Liveness Probe Is Abnormal |
A liveness probe has been configured for the application, and the probe detects an exception. |
The probe detects that the container is normal. |
Major |
Failed to Obtain GPU Resources |
GPU resources could not be obtained during GPU application deployment. |
GPU resources are obtained. |
Critical |
Failed to Obtain GPU Information |
GPU has been enabled on an edge node, and the GPU information fails to be queried. |
The GPU information is successfully queried. |
Critical |
Invalid AK/SK |
EdgeHub has distributed 10 consecutive temporary AK/SK pairs and detects that the AK/SK has expired or is in abnormal state. |
EdgeHub successfully distributes the temporary AK/SK. |
Major |
Application Restarted |
The application container restarts unexpectedly. |
This alarm does not need to be cleared. |
Minor |
NIC Bound to the Container Is Faulty |
The NIC bound to the container is faulty. |
The NIC bound to the container becomes normal. |
Critical |

Setting Alarms on AOM
You can create alarm rules on AOM to monitor metrics of edge nodes. For details, see Creating Threshold Rules.
Reporting User-Defined Alarms to AOM
IEF can report customized alarms from edge nodes to AOM. To be specific, after the MQTT client publishes alarm information to the MQTT broker, IEF will automatically report the alarms to AOM.
For details, see Alarm Reporting and Alarm Clearance.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot