remove article

Author: v-thepet

articles/synapse-analytics/.openpublishing.redirection.synapse-analytics.json

@@ -724,6 +724,11 @@
              "source_path_from_root": "/articles/synapse-analytics/synapse-link/troubleshoot/troubleshoot-sql-snapshot-primary-key-column-order.md",
              "redirect_url": "/azure/synapse-analytics/synapse-link/synapse-link-for-sql-known-issues",
              "redirect_document_id": false
+           },
+           {
+             "source_path_from_root": "/articles/synapse-analytics/monitoring/how-to-monitor-using-azure-monitor.md",
+             "redirect_url": "/azure/synapse-analytics/monitor-synapse-analytics",
+             "redirect_document_id": false
            }
     ]
 }

articles/synapse-analytics/monitor-synapse-analytics-reference.md

@@ -44,47 +44,39 @@ The following table lists the metrics available for the Microsoft.Synapse/worksp
 
 #### Details
 
-- Dedicated SQL pool measures performance in compute data warehouse units (cDWUs). Rather than surfacing details of individual nodes such as memory per node or number of CPUs per node, the intent behind emitting metrics such as `MemoryUsedPercent` and `CPUPercent`  is to show general usage trend over a period of time. These trends help administrators understand how an instance of dedicated SQL pool is utilized, and changes in footprint of memory and/or CPU could be a trigger for actions such as scale-up or scale-down of cDWUs, or investigating queries that might require optimization.
+- Dedicated SQL pool measures performance in compute data warehouse units (DWUs). Rather than surfacing details of individual nodes such as memory per node or number of CPUs per node, metrics such as `MemoryUsedPercent` and `CPUPercent` show general usage trend over a period of time. These trends help administrators understand how a dedicated SQL pool instance is utilized. Changes in memory or CPU footprint could be a trigger for actions such as scale-up or scale-down of DWUs, or investigating queries that might require optimization.
 
-  DWU used represents only a high-level representation of usage across the SQL pool and isn't a comprehensive indicator of utilization. To determine whether to scale up or down, consider all factors that DWU can impact, such as concurrency, memory, `tempdb`, and adaptive cache capacity. [Run your workload at different DWU settings](sql-data-warehouse-manage-compute-overview.md#finding-the-right-size-of-data-warehouse-units) to determine what works best to meet your business objectives.
+  `DWUUsed` represents only high-level usage across the SQL pool and isn't a comprehensive indicator of utilization. To determine whether to scale up or down, consider all factors that DWU can impact, such as concurrency, memory, tempdb size, and adaptive cache capacity. [Run your workload at different DWU settings](sql-data-warehouse/sql-data-warehouse-manage-compute-overview.md#finding-the-right-size-of-data-warehouse-units) to determine what works best to meet your business objectives.
 
-- Memory percentage reflects utilization even if the data warehouse is idle, not active workload memory consumption. Track this metric along with `tempdb` and Gen2 cache to decide whether you need to scale for more cache capacity to increase workload performance.
+- Memory percentage reflects utilization even if the data warehouse is idle, not active workload memory consumption. Track this metric along with tempdb size and Gen2 cache to decide whether you need to scale for more cache capacity to increase workload performance.
 
 - Failed and successful connections are reported for a particular data warehouse, not for the server itself.
 
 [!INCLUDE [horz-monitor-ref-metrics-dimensions-intro](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions-intro.md)]
 
 [!INCLUDE [horz-monitor-ref-metrics-dimensions](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions.md)]
 
-**Microsoft.Synapse/workspaces**
+### Microsoft.Synapse/workspaces
 
-Result, FailureType, Activity, ActivityType, Pipeline, Trigger,<br>
-EventType, TableName, LinkTableStatus, LinkConnectionName,<br>
-SQLPoolName, SQLDatabaseName, JobName, LogicalName, PartitionId, ProcessorInstance
+`Result`, `FailureType`, `Activity`, `ActivityType`, `Pipeline`, `Trigger`, `EventType`, `TableName`, `LinkTableStatus`, `LinkConnectionName`, `SQLPoolName`, `SQLDatabaseName`, `JobName`, `LogicalName`, `PartitionId`, `ProcessorInstance`
 
-Use the `Result` dimension of the `IntegrationActivityRunsEnded`, `IntegrationPipelineRunsEnded`, `IntegrationTriggerRunsEnded`, and `BuiltinSqlPoolDataRequestsEnded` metrics to filter by Succeeded, Failed, or Cancelled final state.
+Use the `Result` dimension of the `IntegrationActivityRunsEnded`, `IntegrationPipelineRunsEnded`, `IntegrationTriggerRunsEnded`, and `BuiltinSqlPoolDataRequestsEnded` metrics to filter by `Succeeded`, `Failed`, or `Canceled` final state.
 
-**Microsoft.Synapse/workspaces/bigDataPools**
+### Microsoft.Synapse/workspaces/bigDataPools
 
-SubmitterId,<br>
-JobState, JobType, JobResult
+`SubmitterId`, `JobState`, `JobType`, `JobResult`
 
-**Microsoft.Synapse/workspaces/kustoPools**
-Database, SealReason,<br>
-ComponentType, ComponentName,<br>
-ContinuousExportName, Result,<br>
-EventStatus, State, RoleInstance,<br>
-IngestionResultDetails, FailureKind,<br>
-MaterializedViewName, Kind, Result,<br>
-QueryStatus, ComponentType, CommandType
+### Microsoft.Synapse/workspaces/kustoPools
 
-**Microsoft.Synapse/workspaces/scopePools**
+`Database`, `SealReason`, `ComponentType`, `ComponentName`, `ContinuousExportName`, `Result`, `EventStatus`, `State`, `RoleInstance`, `IngestionResultDetails`, `FailureKind`, `MaterializedViewName`, `Kind`, `Result`, `QueryStatus`, `ComponentType`, `CommandType`
 
-JobType, JobResult
+### Microsoft.Synapse/workspaces/scopePools
 
-**Microsoft.Synapse/workspaces/sqlPools**
+`JobType`, `JobResult`
 
-IsUserDefined, Result
+### Microsoft.Synapse/workspaces/sqlPools
+
+`IsUserDefined`, `Result`
 
 [!INCLUDE [horz-monitor-ref-resource-logs](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-resource-logs.md)]
 

articles/synapse-analytics/monitor-synapse-analytics.md

@@ -13,9 +13,9 @@ ms.service: synapse-analytics
 
 [!INCLUDE [horz-monitor-intro](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-intro.md)]
 
-## Monitoring methods
+## Synapse Analytics monitoring options
 
-There are several ways to monitor activities in your Synapse Analytics workspace. You can collect and analyze metrics and logs for built-in and serverless SQL pools, dedicated SQL pools, Azure Spark pools, and Data Explorer pools (preview). You can monitor current and historical activities for SQL, Apache Spark, pipelines and triggers, and integration runtimes.
+You can collect and analyze metrics and logs for Azure Synapse Analytics built-in and serverless SQL pools, dedicated SQL pools, Azure Spark pools, and Data Explorer pools (preview). You can monitor current and historical activities for SQL, Apache Spark, pipelines and triggers, and integration runtimes. There are several ways to monitor activities in your Synapse Analytics workspace.
 
 ### Synapse Studio
 
@@ -26,10 +26,10 @@ Open Synapse Studio and navigate to the **Monitor** hub to see a history of all
 
 For more information about monitoring in Synapse Studio, see [Monitor your Synapse Workspace](get-started-monitor.md).
 
-- For information on monitoring pipeline runs, see [Monitor pipeline runs in Synapse Studio](monitoring/how-to-monitor-pipeline-runs.md).
-- For information on monitoring Apache Spark applications, see [Monitor Apache Spark applications in Synapse Studio](monitoring/apache-spark-applications.md).
-- For information on monitoring SQL pools, see [Use Synapse Studio to monitor your SQL pools](monitoring/how-to-monitor-sql-pools.md).
-- For information on monitoring SQL requests, see [Monitor SQL requests in Synapse Studio](monitoring/how-to-monitor-sql-requests.md).
+- For monitoring pipeline runs, see [Monitor pipeline runs in Synapse Studio](monitoring/how-to-monitor-pipeline-runs.md).
+- For monitoring Apache Spark applications, see [Monitor Apache Spark applications in Synapse Studio](monitoring/apache-spark-applications.md).
+- For monitoring SQL pools, see [Use Synapse Studio to monitor your SQL pools](monitoring/how-to-monitor-sql-pools.md).
+- For monitoring SQL requests, see [Monitor SQL requests in Synapse Studio](monitoring/how-to-monitor-sql-requests.md).
 
 ### DMVs and Query Store
 
@@ -61,46 +61,62 @@ Synapse Analytics supports storing monitoring data in Azure Storage or Azure Dat
 
 For lists of available platform metrics for Synapse Analytics, see [Synapse Analytics monitoring data reference](monitor-synapse-analytics-reference.md#metrics).
 
-Synapse Analytics Apache Spark pools support Prometheus metrics and Grafana dashboards. For more information, see [Monitor Apache Spark Applications metrics with Prometheus and Grafana](spark/use-prometheus-grafana-to-monitor-apache-spark-application-level-metrics.md).
+In addition to Log Analytics, Synapse Analytics Apache Spark pools support Prometheus server metrics and Grafana dashboards. For more information, see [Monitor Apache Spark Applications metrics with Prometheus and Grafana](spark/use-prometheus-grafana-to-monitor-apache-spark-application-level-metrics.md) and [Collect Apache Spark applications metrics using Prometheus APIs](connect-monitor-azure-synapse-spark-application-level-metrics.md).
 
 [!INCLUDE [horz-monitor-resource-logs](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-resource-logs.md)]
 
-For the available resource log categories, their associated Log Analytics tables, and the logs schemas for Synapse Analytics, see [Synapse Analytics monitoring data reference](monitor-synapse-analytics-reference.md#resource-logs).
+For the available resource log categories, their associated Log Analytics tables, and the log schemas for Synapse Analytics, see [Synapse Analytics monitoring data reference](monitor-synapse-analytics-reference.md#resource-logs).
 
 [!INCLUDE [horz-monitor-activity-log](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-activity-log.md)]
 
 [!INCLUDE [horz-monitor-analyze-data](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-analyze-data.md)]
 
-For a comparison of using Query Store, DMVs, Log Analytics, or Azure Data Explorer to analyze query history and performance, see [Historical query storage and analysis in Azure Synapse Analytics](query-history-storage-analysis.md).
+In addition to the basic tools, Synapse Analytics supports Query Store, DMVs, or Azure Data Explorer to analyze query history and performance. For a comparison of these analytics methods, see [Historical query storage and analysis in Azure Synapse Analytics](sql/query-history-storage-analysis.md).
 
 [!INCLUDE [horz-monitor-external-tools](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-external-tools.md)]
 
 [!INCLUDE [horz-monitor-kusto-queries](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-kusto-queries.md)]
 
-### Synapse Link table fail events
-Display sample failed Synapse Link table events.
+### Sample queries
+
+**Activity Log query for failed operations**: Lists all reports of failed operations over the past hour. 
+
+```kusto
+AzureActivity 
+| where TimeGenerated > ago(1h)  
+| where ActivityStatus == "Failed"
+```
+
+**Synapse Link table fail events**: Displays failed Synapse Link table events.
 
 ```kusto
 SynapseLinkEvent
 | where OperationName == "TableFail"
 | limit 100
 ```
+
 [!INCLUDE [horz-monitor-alerts](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-alerts.md)]
 
 ### Synapse Analytics alert rules
 
-The following table lists some suggested alerts for Synapse Analytics. These alerts are just examples. You can set alerts for any metric, log entry, or activity log entry that's listed in the [Synapse Analytics monitoring data reference](monitor-synapse-analytics-reference.md).
+The following table lists some suggested alerts for Synapse Analytics. These alerts are just examples. You can set alerts for any metric, log entry, or activity log entry listed in the [Synapse Analytics monitoring data reference](monitor-synapse-analytics-reference.md).
 
 | Alert type | Condition | Description  |
 |:---|:---|:---|
 | Metric| TempDB 75% | Maximum local tempdb used percentage greater than or equal to 75% of threshold value |
-| Metric| DWU Usage near 100% for 1 hour | Average DWU used percentage greater than 95% for one hour |
+| Metric| Data Warehouse Unit (DWU) Usage near 100% | Average DWU used percentage greater than 95% for 1 hour |
 | Log Analytics | SynapseSqlPoolRequestSteps | ShuffleMoveOperation over 10 million rows |
 
 For more details about creating these and other recommended alert rules, see [Create alerts for your Synapse Dedicated SQL Pool](https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/create-alerts-for-your-synapse-dedicated-sql-pool/ba-p/3773256).
 
 [!INCLUDE [horz-monitor-advisor-recommendations](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-advisor-recommendations.md)]
 
+Synapse Analytics dedicated SQL pool provides Azure Advisor recommendations to ensure your data warehouse workload is consistently optimized for performance. For more information, see [Azure Advisor recommendations for dedicated SQL pool in Azure Synapse Analytics](sql-data-warehouse/sql-data-warehouse-concept-recommendations.md).
+
 ## Related content
-- For a reference of the metrics, logs, and other important values created for Synapse Analytics, see [Synapse Analytics monitoring data reference](monitor-synapse-analytics-reference.md).
+
+- For information about monitoring in Synapse Studio, see [Monitor your Synapse Workspace](get-started-monitor.md).
+- For a comparison of Log Analytics, Query Store, DMVs, and Azure Data Explorer analytics, see [Historical query storage and analysis in Azure Synapse Analytics](sql/query-history-storage-analysis.md).
+- For information about Prometheus metrics and Grafana dashboards for Synapse Analytics Apache Spark pools, see [Monitor Apache Spark Applications metrics with Prometheus and Grafana](spark/use-prometheus-grafana-to-monitor-apache-spark-application-level-metrics.md).
+- For a reference of the Azure Monitor metrics, logs, and other important values created for Synapse Analytics, see [Synapse Analytics monitoring data reference](monitor-synapse-analytics-reference.md).
 - For general details on monitoring Azure resources with Azure Monitor, see [Monitor Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource).