Success |
Alert condition not met |
The error message returned because the alert monitoring rule is successfully executed,
but no trigger conditions in the alert monitoring rule are met. For example, if you
set Trigger Condition to errCnt > 100 but the actual value of errCnt is less than 100, no alerts are triggered because
the trigger condition is not met.
|
None |
Notify threshold not reached |
The error message returned because the alert monitoring rule is successfully executed
and a trigger condition is met, but the number of consecutive times that the trigger
condition is met does not reach the value of Threshold of Continuous Triggers. For
example, if you set Threshold of Continuous Triggers to 3, an alert is triggered only
if the trigger condition is met three consecutive times.
|
None |
Successful |
The message returned when the alert monitoring rule is successfully executed and an
alert is triggered.
|
None |
Failed |
CouldNotExecuteQuery *** |
The error message returned because a query statement that is specified in the custom
alert monitoring rule fails to be executed.
|
Modify the query statement in the alert monitoring rule based on the error message.
|
CouldNotExecuteTplQuery *** |
The error message returned because a query statement that is specified in the built-in
alert monitoring rule fails to be executed.
|
Troubleshoot the error based on the error message. Common causes include Logstore
deletion, insufficient access permissions, and Logstore index adjustment.
|
GetQueryRoleTokenError *** |
The error message returned because the role that is specified for the query is invalid.
|
Check whether the role exists and whether the role has the required permissions. |
unknown timespan type |
The error message returned because the time range that is specified for the query
is invalid.
|
Specify a valid time range. |
ExecuteMetaQuery *** |
The error message returned because the specified resource data is invalid. |
Troubleshoot the error based on the error message. Check whether the specified resource
data exists or whether the specified query statement is valid.
|
join configurations and query count should be equal or join config length is invalid |
The error message returned because the number of items that are configured in Query
Statistics does not equal the number of set operations plus 1.
|
Check whether the configurations for set operations are valid. |
severity configurations should have at least 1 or severity count condition err |
The error message returned because no trigger conditions are configured in the alert
monitoring rule.
|
Check whether a trigger condition is specified in the alerting monitoring rule. |
no schedule found or schedule is empty |
The error message returned because Check Frequency in the alert monitoring rule is
empty.
|
Check whether Check Frequency is configured in the alert monitoring rule. |
unsupported time unit or unsupported schedule type |
The error message returned because the value of Check Frequency in the alert monitoring
rule is invalid.
|
Specify a valid value for Check Frequency. |
severity condition err *** |
The error message returned because a trigger condition that is specified in the alert
monitoring rule is invalid.
|
Specify a valid trigger condition. |