- 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?
Managing Access Rules
This section describes how to add, view, and delete access rules.
Prerequisites
- You have created a log group and log stream. For details, see Creating Log Groups and Log Streams. You can also directly create them on the Add Access Rule page.
- You have created a cluster, namespace, and workload by referring to Cloud Container Engine User Guide and also configured a container log collection path.
Adding Access Rules
To map the logs of CCE or custom clusters in AOM to LTS, perform the following steps:
- Log in to the AOM console. In the navigation pane, choose Log > Access LTS.
- Click Add Access Rule.
- Select an access type. Access by Namespace, Access by Workload, or Automatic Mapping are available.
- Access by Namespace: All logs of the selected namespace are connected to the specified log stream.
- Rule Name: Enter a custom rule name.
- Cluster: Select a cluster from the drop-down list.
- Namespace: Select a namespace from the drop-down list.
- Workload: Retain the default value All.
- Container Name: Select a container from the drop-down list box.
- Set an access rule.
- Access all logs: If you select this option, select a log group and log stream.
- Specify log paths: If you select this option, specify a log path and then select a log group and log stream.
NOTE:
If no log group or stream meets your requirements, click Create Log Group or Create Log Stream to create one. After creating a log stream, select an enterprise project.
- Access by Workload: Logs of the selected workload are connected to the specified log stream.
- Rule Name: Enter a custom rule name.
- Cluster: Select a cluster from the drop-down list.
- Namespace: Select a namespace from the drop-down list.
- Workload: Select one or more workloads from the drop-down list.
- Container Name: Select a container from the drop-down list box.
- Set an access rule.
- Access all logs: If you select this option, select a log group and log stream.
- Specify log paths: If you select this option, specify a log path and then select a log group and log stream.
NOTE:
If no log group or stream meets your requirements, click Create Log Group or Create Log Stream to create one. After creating a log stream, select an enterprise project.
- Automatic Mapping: Workload logs are automatically connected to the generated log streams with the same names as the workloads.
- Rule Name: Enter a custom rule name.
- Cluster: Select a cluster from the drop-down list.
- Namespace: Select a namespace from the drop-down list.
- Workload: Select one or more workloads from the drop-down list.
If you select one workload, the rule name is changed to Custom rule name_0 after the rule is created, for example, test_0. If you select multiple workloads, the rule names are changed to Custom rule name_0, Custom rule name_1, and so on, such as test_0 and test_1.
- Set an access rule: Select a log group and an enterprise project, and specify a log stream prefix. A log stream will be generated based on the log stream prefix and workload name. By default, all logs of the selected workload are connected.
- Access by Namespace: All logs of the selected namespace are connected to the specified log stream.
Managing Access Rules
On the Access LTS page, you can search for, view, edit, and delete access rules.
- Search
Click the search box, select a search dimension, for example, Workload, and then select options under this dimension. You can also directly enter a keyword in the search box. In this case, the system searches for information based on access rule names by default.Figure 1 Selecting a search dimension
- View
In the rule list, view the cluster name and namespace of the created rule. Click
in the upper right corner of the search box to customize the display of columns. Click a log group name in the Log Group column to go to the log group details page on the LTS console.
- Edit
Click Edit in the Operation column to edit the access rule. For details about the impact of modifying an access rule, see Modifying a Mapping.
- Delete
Click Delete in the Operation column to delete the access rule. Select one or more access rules and click Delete above the rule list.
NOTE:
Deleted access rules or mapped log streams cannot be recovered. Exercise caution when performing this operation. For details about the impact of deleting an access rule, see Deleting a Mapping.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.