Their information for relevant alarm channels (SMS and email) has not been verified. Please verify the information in the CAM console.
Yes. You can create a new recipient group based on your business needs to prevent individual users from receiving repeated alarm notifications.
Yes. An alarm notification will be sent to the recipients after the corresponding alarm is resolved.
No. After a user disassociates a CVM instance from the default policy, it will not be automatically associated again on the backend.
No. The alarm switch is only used to disable a no longer needed alarm policy and will not change the alarm status.
There is only one default policy for each project in each policy type. The default policy is automatically created after you purchase an instance, which can be modified but not deleted.
Cloud Monitor will automatically create a default CVM alarm policy (alarms will be triggered when disks become read-only or unreachable ping occurs) and a default TencentDB policy (alarms will be triggered if the used disk capacity is greater than 90 MB or disk utilization exceeds 80% for 5 minutes).
For the default alarm policy created by the system, you need to associate it with an alarm recipient group before alarm notifications can be received.
Currently, the default alarm policy is supported only by CVM, TencentDB for MySQL, TencentDB for Redis, TencentDB for SQL Server, TencentDB for MongoDB, TencentDB for MariaDB, API Gateway, and Direct Connect. Other Tencent Cloud products will support it in the future. If you have any questions, please submit a ticket for assistance.
The system's data monitoring has a certain latency. It is normal to still receive alarm notifications for a short period of time after the alarm policy is disassociated from a CVM instance.
Currently, it cannot be modified.
Basic Tencent Cloud resource monitoring and custom monitoring use different sub-account permissions. A sub-account has no permission to query information of other sub-accounts by default. After the Cloud Monitor root account grants the
QcloudMonitorFullAccess permission to a sub-account, alarm recipients configured in basic Tencent Cloud resource monitoring cannot be synced to custom monitoring. If the sub-account needs to read configured alarm recipients in custom monitoring, you need to log in to the CAM module with the root account and grant the
QcloudCamReadOnlyAccess permission to the sub-account.
|Not resolved||An alarm has not been processed or is being processed.|
|Resolved||Normal status has been restored|
a.comwhich then is migrated to project B?
The CDN domain name policy of project A will be automatically disassociated from the domain name
a.com. If the domain name
a.com is not associated with any CDN domain name alarm policy, no alarm will be triggered. The automatic disassociation logic is implemented once every day, so it is normal if the data on the console is not up-to-date.