- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Getting Started with MAS
- Modules
- Namespace
- Multi-Active Instances
- Application Management
- Monitor Management
- Credential Management
- Event Monitoring
- Audit Logs
- Permissions Management
-
FAQs
-
MAS FAQs
- Is MAS a Product or Solution?
- Does MAS Synchronize Data in Addition to Controlling Access from Applications to Databases?
- Is MAS Like a Management Channel for Which I Need to Configure Automatic Switchover Policies?
- What Is the Automatic Switchover Mechanism? How Does MAS Implement Switchovers in Seconds?
-
Multi-Active DR Solution FAQs
- In the Single- or Dual-Instance Data Layer Architecture (Same Region, Multi-AZ, Traffic Distribution with API Gateway), Which Components Are Provided by MAS and Which Ones Should I Prepare?
- Can I Implement the Active-Active Solution on Any Other Services in Addition to Self-Built Cloud Services?
- How Do I Implement Database Dual-Write?
- Does the Multi-Active Architecture Have Any Requirements on My Services?
- What Are the RPO and RTO of the Multi-Active DR Solution?
- Does the Multi-Active DR Solution Have Any Network Requirements? Will Incorrect Switchover Occur If the Network is Unstable or Jitters?
- How Do I Configure Monitoring for Multi-AZ Deployment in the Same Region?
- Will MAS and API Gateway Be Deployed on Both Huawei Cloud and Our Cloud?
- MAS Usage FAQs
-
MAS FAQs
- General Reference
Show all
Copied.
Events Supported by Event Monitoring
Source |
Name |
Severity |
Description |
Solution |
Impact |
---|---|---|---|---|---|
MAS |
Abnormal database |
Critical |
Abnormal relational database is detected by the MAS MySQL/Oracle/PostgreSQL monitor. |
On the MAS console, click Multi-Active Instances, choose an instance, and check event MySQL/Oracle/PostgreSQL details and rectify the faults. |
Data in the relational database may be lost. |
MAS |
Database recovered |
Major |
The relational database is recovered, detected by the MySQL/Oracle/PostgreSQL monitor. |
None |
None |
MAS |
Abnormal Redis database |
Critical |
Abnormal Redis database is detected by the MAS Redis monitor. |
On the MAS console, click Multi-Active Instances, choose an instance, and view Redis event details and rectify the faults. |
Data in the Redis database may be lost. |
MAS |
Redis database recovered |
Major |
The Redis database is recovered. |
None |
None |
MAS |
Abnormal MongoDB database |
Critical |
Abnormal MongoDB database is detected by the MAS MongoDB monitor. |
On the MAS console, click Multi-Active Instances, choose an instance, and view MongoDB event details and rectify the faults. |
Data in the MongoDB database may be lost. |
MAS |
MongoDB database recovered |
Major |
The MongoDB database is recovered. |
None |
None |
MAS |
Abnormal Elasticsearch |
Critical |
Abnormal Elasticsearch database is detected by the MAS Elasticsearch monitor. |
On the MAS console, click Multi-Active Instances, choose an instance, and view Elasticsearch event details and rectify the faults. |
The Elasticsearch instance may be unavailable. |
MAS |
Elasticsearch instance recovered |
Major |
The Elasticsearch database is recovered. |
None |
None |
MAS |
Abnormal API |
Critical |
Abnormal API or unexpected response code is detected by the MAS API monitor. |
On the MAS console, click Multi-Active Instances, choose an instance, and view API event details and rectify the faults. |
API data in the database may be lost. |
MAS |
API recovered |
Major |
The API is recovered. |
None |
None |
MAS |
Area status changed |
Major |
Area status changes are detected by MAS. |
On the MAS console, click Multi-Active Instances, choose an instance, and view multi-active area event details and rectify the faults. |
Network of the multi-active areas may change. |
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