What Can I Do If an AS Policy Fails to Be Enabled?
- Description: The alarm rule does not exist.
Possible cause: The alarm rule used in the alarm policy is deleted.
Handling method: Change the alarm rule used in the alarm policy and enable the AS policy again.
- Description: The triggering time of the periodic policy falls outside the effective time range of the policy.
Possible cause: The periodic policy has expired.
Handling method: Change the start time and end time of the periodic policy and enable the policy again.
- Description: The triggering time of the scheduled policy must be later than the current time.
Possible causes: The triggering time of the scheduled policy has expired.
Handling method: Change the triggering time of the scheduled policy and enable the policy again.
- Description: A system error has occurred.
Handling method: Try again later or contact technical support.
AS Policy FAQs
- How Many AS Policies Can I Enable?
- What Are the Conditions to Trigger an Alarm-based AS Policy?
- What Is a Cooldown Period and Why Is It Required?
- Can AS Scale Capacity Based on Custom Monitoring by Cloud Eye?
- What Monitoring Metrics for an AS Group Will Be Affected If VM Tools Are Not Installed on the Instances in the Group?
- What Can I Do If an AS Policy Fails to Be Enabled?
- How Do I Install the Agent on Instances in an AS Group to Use Agent Monitoring Metrics?
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.
Chatbotmore
