Simple Log Service:Error codes for alert monitoring

Execution result

Details

Description

Solution

Success

Alert condition not met

The alert monitoring rule ran successfully, but the results did not meet the trigger condition. For example, if you set the trigger condition to errCnt > 100 and the actual value is less than 100, an alert is not triggered.

None

Notify threshold not reached

The alert monitoring rule ran successfully and the trigger condition was met, but the consecutive trigger threshold was not reached. For example, if you set the consecutive trigger threshold to 3, an alert is triggered only after the condition is met three consecutive times.

None

Successful

The alert monitoring rule ran successfully and triggered an alert.

None

Failed

CouldNotExecuteQuery ***

The query and analysis statement in the custom alert monitoring rule failed to execute.

Modify the query and analysis statement in the alert monitoring rule based on the error message.

CouldNotExecuteTplQuery ***

The query and analysis statement in the built-in alert monitoring rule failed to execute.

Troubleshoot the issue based on the error message. Common causes include a deleted Logstore, insufficient access permissions, or a modified Logstore index.

GetQueryRoleTokenError ***

The role specified for query and analysis is invalid.

Check whether the authorized role for query and analysis exists and has the required permissions.

unknown timespan type

The specified query time range is invalid.

Set a valid query time range.

ExecuteMetaQuery ***

The query for resource data failed.

Troubleshoot the issue based on the error message. Confirm that the resource data exists and the query statement is correct.

join configurations and query count should be equal or join config length is invalid

The number of collection operation configurations is not equal to the number of query statistics configurations minus one.

Check the collection operation configuration.

severity configurations should have at least 1 or severity count condition err

An alert monitoring rule must contain at least one trigger condition.

Verify that at least one trigger condition is set for the alert monitoring rule.

no schedule found or schedule is empty

The check frequency is not set in the alert monitoring rule.

Verify that a check frequency is set for the alert monitoring rule.

unsupported time unit or unsupported schedule type

The check frequency specified in the alert monitoring rule is invalid.

Set a valid check frequency.

severity condition err ***

The trigger condition in the alert monitoring rule is invalid.

Set a valid trigger condition.

Error message

Description

Solution

parameter not found

A variable in the conditional expression does not exist.

Check whether the conditional expression uses a field that does not exist in the query results.

evaluated more than 1000 times

After 1,000 calculations, the expression did not evaluate to true for any log.

Modify the conditional expression.

Notify threshold not reached

The total number of triggers did not reach the notification threshold.

Adjust the notification threshold.

result type is not bool

The result of the expression is not a Boolean type.

Modify the conditional expression to return a Boolean result.

Notification has been disabled

Notifications are disabled.

Enable notifications on the alert list page.

Notification throttled

The notification interval has not elapsed since the last notification was sent.

Adjust the notification interval.

Notification not configured

No notification is configured for the alert rule.

Add a notification configuration.

Alert condition not met

The conditional expression evaluated to false and did not meet the trigger condition.

If this result is expected, the configuration is correct, but no alert was triggered. If this result is not expected, modify the conditional expression.