The alarm recipients’ 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 restored.
No. After a user disassociates a CVM instance from the default policy, it will not be automatically associated again on the backend.
No. Stopping and restarting an alarm are only useful for disabling 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 will be 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 ping becomes unreachable) 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 only supported 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 the default alarm policy in the future. If you have any questions, please submit a ticket for assistance.
Because the system's data monitoring has 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 does not have permission to query information about other sub-accounts by default. After the Cloud Monitor root account grants the
QcloudMonitorFullAccess permission to a sub-account, the configured alarm recipients of basic Tencent Cloud resources monitoring cannot be synced with the alarm recipients of 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 restored: an alarm has not been processed or is being processed.
Restored: an alarm has been restored to its normal state.
Insufficient data: either the alarm policy that generated the alarm has been deleted, the CVM instance has migrated from one project to another, or no data is reported as Agent is not installed or has been uninstalled.
a.com, which is then migrated to project B?
The CDN domain name policy of project A will automatically be disassociated from the domain
a.com. After disassociation, if the domain
a.com is not associated with any other CDN domain name alarm policies, no alarm will be triggered. The automatic disassociation logic will be implemented once every day. The console data may have an update delay, which is normal.