- 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.
Configuring Monitors
This section describes how to configure parameters for all monitors under an instance.
Note that these configurations will not change the Advanced settings configured in monitor creation.
Procedure
- Log in to the MAS console. On the Multi-Active Instances page, click an instance to go to its console.
- Click the Monitor List tab and click Configure Monitoring.
- Configure the parameters and click OK. You are advised to retain the default settings.
Table 1 Monitoring configurations Parameter
Description
Monitor Type
The type of the monitor to be configured. Only monitors created under the instance are displayed.
Monitoring Timeout (ms)
The timeout duration before a monitor becomes abnormal, in milliseconds.
Value range: 4000 to 400,000
Retry Interval (ms)
Retry Interval (ms)
Value range: 2000 to 30,000
Database Access Timeout (ms)
This is required only for MySQL, Oracle, PostgreSQL, and MongoDB monitors.
The database access timeout duration, over which the database access is considered failed.
Value range: 3000 to 100,000
Healthy Threshold
How many workers are required to confirm the database health. For example, 1 indicates that as long as one worker in the monitoring cluster detects the database, the detection is considered successful. If the detection fails, the leader will handle the fault.
Enter 1 or 2.
NOTE:
For API monitors, only Healthy Threshold needs to be configured.
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