- What's New
- Function Overview
- Service Overview (2.0)
- Getting Started (2.0)
-
User Guide (2.0)
- Introduction
- Access Center
- Dashboard
- Alarm Management
- Metric Browsing
- Log Analysis
-
Prometheus Monitoring
- Prometheus Monitoring
- Creating Prometheus Instances
- Managing Prometheus Instances
- Configuring a Recording Rule
- Metric Management
- Dashboard Monitoring
-
Access Guide
- Connecting Node Exporter
-
Exporter Access in the VM Scenario
- Access Overview
- MySQL Component Access
- Redis Component Access
- Kafka Component Access
- Nginx Component Access
- MongoDB Component Access
- Consul Component Access
- HAProxy Component Access
- PostgreSQL Component Access
- Elasticsearch Component Access
- RabbitMQ Component Access
- Access of Other Components
- Custom Plug-in Access
- Other Operations
- Obtaining the Service Address of a Prometheus Instance
- Viewing Prometheus Instance Data Through Grafana
- Reading Prometheus Instance Data Through Remote Read
- Reporting Self-Built Prometheus Instance Data to AOM
- Resource Usage Statistics
- Business Monitoring (Beta)
- Infrastructure Monitoring
- Settings
- Remarks
- Permissions Management
- Auditing
- Subscribing to AOM 2.0
- Upgrading to AOM 2.0
- Best Practices (2.0)
-
FAQs (2.0)
- Overview
- Dashboard
- Alarm Management
- Log Analysis
- Prometheus Monitoring
- Infrastructure Monitoring
-
Collection Management
- Are ICAgent and UniAgent the Same?
- What Can I Do If an ICAgent Is Offline?
- Why Is an Installed ICAgent Displayed as "Abnormal" on the Agent Management Page?
- Why Can't I View the ICAgent Status After It Is Installed?
- Why Can't AOM Monitor CPU and Memory Usage After ICAgent Is Installed?
- How Do I Obtain an AK/SK?
- FAQs About ICAgent Installation
- How Do I Enable the Nginx stub_status Module?
- Other FAQs
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs
-
Alarm
- Querying the Event Alarm Rule List
- Adding an Event Alarm Rule
- Modifying an Event Alarm Rule
- Deleting an Event Alarm Rule
- Obtaining the Alarm Sending Result
- Deleting a Silence Rule
- Adding a Silence Rule
- Modifying a Silence Rule
- Obtaining the Silence Rule List
- Querying an Alarm Action Rule Based on Rule Name
- Adding an Alarm Action Rule
- Deleting an Alarm Action Rule
- Modifying an Alarm Action Rule
- Querying the Alarm Action Rule List
- Querying Metric or Event Alarm Rules
- Adding or Modifying Metric or Event Alarm Rules
- Deleting Metric or Event Alarm Rules
- Querying Events and Alarms
- Counting Events and Alarms
- Reporting Events and Alarms
-
Monitoring
- Querying Time Series Objects
- Querying Time Series Data
- Querying Metrics
- Querying Monitoring Data
- Adding Monitoring Data
- Adding or Modifying One or More Service Discovery Rules
- Deleting a Service Discovery Rule
- Querying Existing Service Discovery Rules
- Adding a Threshold Rule
- Querying the Threshold Rule List
- Modifying a Threshold Rule
- Deleting a Threshold Rule
- Querying a Threshold Rule
- Deleting Threshold Rules in Batches
-
Prometheus Monitoring
- Querying Expression Calculation Results in a Specified Period Using the GET Method
- (Recommended) Querying Expression Calculation Results in a Specified Period Using the POST Method
- Querying the Expression Calculation Result at a Specified Time Point Using the GET Method
- (Recommended) Querying Expression Calculation Results at a Specified Time Point Using the POST Method
- Querying Tag Values
- Obtaining the Tag Name List Using the GET Method
- (Recommended) Obtaining the Tag Name List Using the POST Method
- Querying Metadata
- Log
- Prometheus Instance
- Configuration Management
-
Alarm
- Historical APIs
- Examples
- Permissions Policies and Supported Actions
- Appendix
- SDK Reference
-
Service Overview (1.0)
- What Is AOM?
- Product Architecture
- Functions
- Application Scenarios
- Edition Differences
-
Metric Overview
- Introduction
- Network Metrics and Dimensions
- Disk Metrics and Dimensions
- Disk Partition Metrics
- File System Metrics and Dimensions
- Host Metrics and Dimensions
- Cluster Metrics and Dimensions
- Container Metrics and Dimensions
- VM Metrics and Dimensions
- Instance Metrics and Dimensions
- Service Metrics and Dimensions
- Restrictions
- Privacy and Sensitive Information Protection Statement
- Relationships Between AOM and Other Services
- Basic Concepts
- Permissions
- Billing
- Getting Started (1.0)
-
User Guide (1.0)
- Overview
- Subscribing to AOM
- Permissions Management
- Connecting Resources to AOM
- Monitoring Overview
- Alarm Management
- Resource Monitoring
- Log Management
- Configuration Management
- Auditing
- Upgrading to AOM 2.0
- Best Practices (1.0)
-
FAQs (1.0)
- User FAQs
-
Consultation FAQs
- What Are the Usage Restrictions of AOM?
- What Are the Differences Between AOM and APM?
- How Do I Distinguish Alarms from Events?
- What Is the Relationship Between the Time Range and Statistical Cycle?
- Does AOM Display Logs in Real Time?
- How Can I Do If I Cannot Receive Any Email Notification After Configuring a Threshold Rule?
- Why Are Connection Channels Required?
-
Usage FAQs
- What Can I Do If I Do Not Have the Permission to Access SMN?
- What Can I Do If Resources Are Not Running Properly?
- How Do I Set the Full-Screen Online Duration?
- What Can I Do If the Log Usage Reaches 90% or Is Full?
- How Do I Obtain an AK/SK?
- How Can I Check Whether a Service Is Available?
- Why Is the Status of an Alarm Rule Displayed as "Insufficient"?
- Why the Status of a Workload that Runs Normally Is Displayed as "Abnormal" on the AOM Page?
- How Do I Create the apm_admin_trust Agency?
- What Is the Billing Policy of Logs?
- Why Can't I See Any Logs on the Console?
- What Can I Do If an ICAgent Is Offline?
- Why Can't the Host Be Monitored After ICAgent Is Installed?
- Why Is "no crontab for root" Displayed During ICAgent Installation?
- Why Can't I Select an OBS Bucket When Configuring Log Dumping on AOM?
- Why Can't Grafana Display Content?
Creating an Event Alarm Rule
You can set event conditions for services by setting event alarm rules. When the resource data meets an event condition, an event alarm is generated.
Precautions
If you want to receive email or SMS notifications when the resource data meets the event condition, set an alarm action rule according to Creating an Alarm Action Rule.
Procedure
- Log in to the AOM console. In the navigation pane, choose Alarm Center > Alarm Rules. Then, click Create Alarm Rule in the upper right corner.
- Set an event alarm rule.
- Set basic information such as the rule name and description.
Figure 1 Setting basic information
- Set details about the rule.
- Set Rule Type to Event alarm.
- Set the alarm source, trigger object, and trigger policy.
Table 1 Alarm rule parameters Parameter
Description
Alarm Source
Name of the service for which an event alarm is reported. You can select a service from the service list.
Trigger Object
Select criteria to filter service events. You can select Notification Type, Event Name, Alarm Severity, Custom Attributes, Namespace, or Cluster Name as the filter criterion. One or more criteria can be selected.
Trigger Policy
Policy for triggering event alarms.
- Accumulated Triggering: An alarm action rule is triggered when the accumulated number of times you preset is reached in a monitoring period.
- Immediate Triggering: An alarm is generated immediately when the filter criterion is met.
Figure 2 Setting an alarm rule
- Set an alarm notification policy. There are two alarm notification modes.
- Direct Alarm Reporting: An alarm is directly sent when the alarm condition is met.
You need to configure whether to enable an alarm action rule. After this function is enabled, the system sends alarm notifications based on the associated SMN topic and message template. If the existing alarm action rules cannot meet your requirements, click Create Rule to create one. For details, see Creating an Alarm Action Rule.
Figure 3 Selecting the direct alarm reporting mode - Alarm Noise Reduction: Alarms are sent only after being processed based on noise reduction rules, preventing alarm storms.
Select a grouping rule from the drop-down list. If existing grouping rules cannot meet your requirements, click Create Rule to create one. For details, see Creating a Grouping Rule.
Figure 4 Selecting the alarm noise reduction mode
- Direct Alarm Reporting: An alarm is directly sent when the alarm condition is met.
- Set basic information such as the rule name and description.
- Click Create Now. An event alarm rule is created, as shown in the following figure.
This rule monitors critical alarm events of AOM. When a service event meets the preset notification policy, the system sends an alarm notification to specified personnel by email or SMS.
Figure 5 Event alarm rule
Related Operations
After creating an event alarm rule, perform the operations listed in Table 2 if needed.
Operation |
Description |
---|---|
Editing an event alarm rule |
Click Edit in the Operation column. |
Deleting event alarm rules |
|
Migrating event alarm rules |
To migrate one or more event alarm rules, select the check boxes before them and click Migrate to AOM 2.0 above the rule list.
NOTICE:
Migration cannot be undone. Exercise caution when performing this operation. |
Starting or stopping an event alarm rule |
Click Start or Stop in the Operation column. |
Searching for an event alarm rule |
You can search for a rule by rule name, description, or metric name. Simply enter a keyword in the search box in the upper right corner and click |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.