Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Show all

Step 5: Configure Alarm Rules

Updated on 2023-05-06 GMT+08:00

This section describes the alarm rules of some metrics and how to configure them. In actual services, you are advised to configure alarm rules for metrics based on the following alarm policies.

NOTE:

Approach Upper Limit in the following table indicates whether the performance of the current resource is close to the upper limit. If the performance is close to the upper limit, the performance supported by the current resource is the alarm threshold set in the alarm policy. If the performance continues to increase, services may become abnormal.

Table 1 Kafka instance metrics to configure alarm rules for

Metric ID

Metric

Alarm Policy

Metric Description and Alarm Handling

broker_disk_usage

Disk Capacity Usage

Alarm threshold: original value > 80%

Number of consecutive periods: 1

Alarm severity: critical

Metric description: disk usage of the Kafka VM.

Alarm handling: Modify the instance storage space. For details, see Modifying Instance Specifications.

broker_cpu_core_load

Average Load per CPU Core

Alarm threshold: original value > 2

Number of consecutive periods: 3

Alarm severity: major

Metric description: average load of each CPU core of the Kafka VM.

Alarm handling: Check whether the metric has been approaching or exceeding the alarm threshold for a long time. If yes, modify the instance bandwidth or the number of brokers. For details, see Modifying Instance Specifications.

broker_memory_usage

Memory Usage

Alarm threshold: original value > 90%

Number of consecutive periods: 3

Alarm severity: critical

Metric description: memory usage of the Kafka VM.

Alarm handling: Modify the instance bandwidth or the number of brokers. For details, see Modifying Instance Specifications.

current_partitions

Partitions

Alarm threshold: original value > 90% of the maximum allowed number of partitions. The partition limit varies depending on instance specifications. For details, see Specifications.

Number of consecutive periods: 1

Alarm severity: major

Metric description: number of used partitions in the instance.

Alarm handling: If new topics are required, modify the instance bandwidth or the number of brokers, or split the service to multiple instances. For details about how to modify the instance bandwidth or the number of brokers, see Modifying Instance Specifications.

broker_cpu_usage

CPU Usage

Alarm threshold: original value > 90%

Number of consecutive periods: 3

Alarm severity: major

Metric description: CPU usage of the Kafka VM.

Alarm handling: Check whether the metric has been approaching or exceeding the alarm threshold for a long time. If yes, modify the instance bandwidth or the number of brokers. For details, see Modifying Instance Specifications.

group_msgs

Accumulated Messages

Alarm threshold: original value > 90% of the upper limit. The upper limit is customized.

Number of consecutive periods: 1

Alarm severity: major

Metric description: total number of accumulated messages in all consumer groups of the instance.

Alarm handling: Delete idle consumer groups, if any. You can also accelerate message retrieval, for example, by increasing the number of consumers.

topic_messages_remained

Topic Available Messages

Alarm threshold: original value > 90% of the upper limit. The upper limit is customized.

Number of consecutive periods: 1

Alarm severity: major

Metric description: number of remaining messages that can be retrieved from the specified topic in the consumer group.

Alarm handling: Check whether the consumer code logic is correct, for example, by checking whether the consumer stops consuming messages due to an exception. You can also accelerate message retrieval, for example, by adding topic consumers. Ensure that the number of partitions is greater than or equal to the number of consumers.

Procedure

  1. Log in to the Kafka console, and select the region where the Kafka instance is located.
  2. Click next to the Kafka instance name to go to the instance monitoring page of the Cloud Eye console.
  3. Hover the mouse pointer over a metric and click to create an alarm rule for the metric.
  4. Specify the alarm details.

    For more information about creating alarm rules, see Creating an Alarm Rule.

    1. Set the alarm name and description.
    2. Specify the alarm policy and alarm severity.

      As shown in the following figure, if the original disk capacity usage exceeds 85% for three consecutive periods, an alarm is generated. If the alarm is not handled on time, an alarm notification is sent.

      Figure 1 Setting the alarm policy and alarm severity
    3. Set the alarm notification configurations. If you enable Alarm Notification, set the validity period, notification object, and trigger condition.
    4. Click Create.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback