You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/insights/azure-sql.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -174,7 +174,7 @@ AzureMetrics
174
174
175
175
> [!NOTE]
176
176
>
177
-
> - Pre-requirement of setting up this alert is that monitored databases stream basic metrics to Azure SQL Analytics.
177
+
> - Pre-requirement of setting up this alert is that monitored databases stream basic metrics to the Log Analytics workspace used by Azure SQL Analytics.
178
178
> - Replace the MetricName value `cpu_percent` with `dtu_consumption_percent` to obtain high DTU results instead.
179
179
180
180
#### High CPU on elastic pools
@@ -190,7 +190,7 @@ AzureMetrics
190
190
191
191
> [!NOTE]
192
192
>
193
-
> - Pre-requirement of setting up this alert is that monitored databases stream Basic metrics to Azure SQL Analytics.
193
+
> - Pre-requirement of setting up this alert is that monitored databases stream Basic metrics to the Log Analytics workspace used by Azure SQL Analytics.
194
194
> - Replace the MetricName value `cpu_percent` with `dtu_consumption_percent` to obtain high DTU results instead.
195
195
196
196
#### Storage in average above 95% in the last 1 hr
@@ -208,7 +208,7 @@ AzureMetrics
208
208
209
209
> [!NOTE]
210
210
>
211
-
> - Pre-requirement of setting up this alert is that monitored databases stream basic metrics to Azure SQL Analytics.
211
+
> - Pre-requirement of setting up this alert is that monitored databases stream basic metrics to the Log Analytics workspace used by Azure SQL Analytics.
212
212
> - This query requires an alert rule to be set up to fire off an alert when there exist results (> 0 results) from the query, denoting that the condition exists on some databases. The output is a list of database resources that are above the `storage_threshold` within the `time_range` defined.
213
213
> - The output is a list of database resources that are above the `storage_threshold` within the `time_range` defined.
214
214
@@ -229,7 +229,7 @@ AzureDiagnostics
229
229
230
230
> [!NOTE]
231
231
>
232
-
> - Pre-requirement of setting up this alert is that monitored databases stream SQLInsights diagnostics log to Azure SQL Analytics.
232
+
> - Pre-requirement of setting up this alert is that monitored databases stream SQLInsights diagnostics log to the Log Analytics workspace used by Azure SQL Analytics.
233
233
> - This query requires an alert rule to be set up to run with the same frequency as `alert_run_interval` in order to avoid duplicate results. The rule should be set up to fire off the alert when there exist results (> 0 results) from the query.
234
234
> - Customize the `alert_run_interval` to specify the time range to check if the condition has occurred on databases configured to stream SQLInsights log to Azure SQL Analytics.
235
235
> - Customize the insights_string to capture the output of the Insights root cause analysis text. This is the same text displayed in the UI of Azure SQL Analytics that you can use from the existing insights. Alternatively, you can use the query below to see the text of all Insights generated on your subscription. Use the output of the query to harvest the distinct strings for setting up alerts on Insights.
@@ -255,7 +255,7 @@ AzureDiagnostics
255
255
256
256
> [!NOTE]
257
257
>
258
-
> - Pre-requirement of setting up this alert is that the monitored managed instance has the streaming of ResourceUsageStats log enabled to Azure SQL Analytics.
258
+
> - Pre-requirement of setting up this alert is that the monitored managed instance has the streaming of ResourceUsageStats log enabled to the Log Analytics workspace used by Azure SQL Analytics.
259
259
> - This query requires an alert rule to be set up to fire off an alert when there exist results (> 0 results) from the query, denoting that the condition exists on the managed instance. The output is storage percentage consumption on the managed instance.
260
260
261
261
#### CPU average consumption is above 95% in the last 1 hr
@@ -271,7 +271,7 @@ AzureDiagnostics
271
271
272
272
> [!NOTE]
273
273
>
274
-
> - Pre-requirement of setting up this alert is that the monitored managed instance has the streaming of ResourceUsageStats log enabled to Azure SQL Analytics.
274
+
> - Pre-requirement of setting up this alert is that the monitored managed instance has the streaming of ResourceUsageStats log enabled to the Log Analytics workspace used by Azure SQL Analytics.
275
275
> - This query requires an alert rule to be set up to fire off an alert when there exist results (> 0 results) from the query, denoting that the condition exists on the managed instance. The output is average CPU utilization percentage consumption in defined period on the managed instance.
276
276
277
277
### Pricing
@@ -282,4 +282,4 @@ While Azure SQL Analytics (preview) is free to use, consumption of diagnostics t
282
282
283
283
- Use [log queries](../logs/log-query-overview.md) in Azure Monitor to view detailed Azure SQL data.
284
284
-[Create your own dashboards](../visualize/tutorial-logs-dashboards.md) showing Azure SQL data.
285
-
-[Create alerts](../alerts/alerts-overview.md) when specific Azure SQL events occur.
285
+
-[Create alerts](../alerts/alerts-overview.md) when specific Azure SQL events occur.
0 commit comments