Skip to content

Commit 1b18241

Browse files
Merge pull request #248811 from yelevin/yelevin-patch-1
Added remediation for excessive resource usage
2 parents 3610934 + 4e32460 commit 1b18241

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/sentinel/monitor-analytics-rule-integrity.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -156,14 +156,14 @@ For either **Scheduled analytics rule run** or **NRT analytics rule run**, you m
156156
| An internal server error occurred while running the query. | |
157157
| The query execution timed out. | |
158158
| A table referenced in the query was not found. | Verify that the relevant data source is connected. |
159-
| A semantic error occurred while running the query. | Try resetting the alert rule by editing and saving it (without changing any settings). |
159+
| A semantic error occurred while running the query. | Try resetting the analytics rule by editing and saving it (without changing any settings). |
160160
| A function called by the query is named with a reserved word. | Remove or rename the function. |
161-
| A syntax error occurred while running the query. | Try resetting the alert rule by editing and saving it (without changing any settings). |
161+
| A syntax error occurred while running the query. | Try resetting the analytics rule by editing and saving it (without changing any settings). |
162162
| The workspace does not exist. | |
163-
| This query was found to use too many system resources and was prevented from running. | |
163+
| This query was found to use too many system resources and was prevented from running. | Review and tune the analytics rule. Consult our Kusto Query Language [overview](kusto-overview.md) and [best practices](/azure/data-explorer/kusto/query/best-practices?toc=%2Fazure%2Fsentinel%2FTOC.json&bc=%2Fazure%2Fsentinel%2Fbreadcrumb%2Ftoc.json) documentation. |
164164
| A function called by the query was not found. | Verify the existence in your workspace of all functions called by the query. |
165165
| The workspace used in the query was not found. | Verify that all workspaces in the query exist. |
166-
| You don't have permissions to run this query. | Try resetting the alert rule by editing and saving it (without changing any settings). |
166+
| You don't have permissions to run this query. | Try resetting the analytics rule by editing and saving it (without changing any settings). |
167167
| You don't have access permissions to one or more of the resources in the query. | |
168168
| The query referred to a storage path that was not found. | |
169169
| The query was denied access to a storage path. | |

0 commit comments

Comments
 (0)