AOM Best Practices

This document summarizes Application Operations Management (AOM) best practices and provides solutions and operation guide to help you easily use AOM.

**Table 1** AOM best practices
Best Practice	Description
Preventing ELB Alarm Storms Using AOM Alarm Grouping Rules	This section describes how to set alarm noise reduction. Before sending an alarm notification, AOM processes alarms based on noise reduction rules to prevent alarm storms.
Automatically Connecting to UniAgent Using Custom Images	This section describes how to package images for connecting UniAgent in the Linux and Windows environments. By using the images, you can purchase an ECS and UniAgent will then be automatically installed on it.
Connecting Self-Built Middleware to AOM in the CCE Container Scenario for Metric Monitoring	Prometheus monitoring provides multiple common middleware Exporters. AOM is compatible with native Prometheus. You can install Exporters in the community to connect self-built middleware to AOM in the CCE container scenario.
Generating Alarms by Tag	Through Prometheus monitoring and alarm management, alarms can be generated for resources by tag. This section describes how to generate alarms for the CPU usage of a Distributed Cache Service (DCS) instance by tag.

Next topic: Preventing ELB Alarm Storms Using AOM Alarm Grouping Rules

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel