Curate for Monitor duplication

Author: cdpark

articles/stream-analytics/debug-locally-using-job-diagram-vs-code.md

@@ -51,7 +51,7 @@ In this section, you explore the metrics available for each part of the diagram.
    > [!div class="mx-imgBorder"]
    > ![Job diagram metrics](./media/debug-locally-using-job-diagram-vs-code/job-metrics.png)
 
-3. Select the name of the input data source from the dropdown to see input metrics. The input source in the screenshot below is called *quotes*. For more information about input metrics, see [Azure Stream Analytics job metrics](./stream-analytics-job-metrics.md).
+3. Select the name of the input data source from the dropdown to see input metrics. The input source in the screenshot below is called *quotes*. For more information about input metrics, see [Azure Stream Analytics job metrics](monitor-azure-stream-analytics-reference.md#metrics).
 
    > [!div class="mx-imgBorder"]
    > ![Job diagram input metrics](./media/debug-locally-using-job-diagram-vs-code/input-metrics.png)
@@ -61,7 +61,7 @@ In this section, you explore the metrics available for each part of the diagram.
    > [!div class="mx-imgBorder"]
    > ![Step metrics](./media/debug-locally-using-job-diagram-vs-code/step-metrics.png)
 
-5. Select an output in the diagram or from the dropdown to see output-related metrics. For more information about output metrics, see [Azure Stream Analytics job metrics](./stream-analytics-job-metrics.md). Live output sinks aren't supported.
+5. Select an output in the diagram or from the dropdown to see output-related metrics. For more information about output metrics, see [Azure Stream Analytics job metrics](monitor-azure-stream-analytics-reference.md#metrics). Live output sinks aren't supported.
 
    > [!div class="mx-imgBorder"]
    > ![Output metrics](./media/debug-locally-using-job-diagram-vs-code/output-metrics.png)

articles/stream-analytics/event-ordering.md

@@ -76,5 +76,5 @@ When a partition doesn't have any data for more than the configured late arrival
 
 ## Next steps
 * [Time handling considerations](stream-analytics-time-handling.md)
-* [Azure Stream Analytics job metrics](./stream-analytics-job-metrics.md)
-* [Azure Stream Analytics metrics dimensions](./stream-analytics-job-metrics-dimensions.md)
+* [Azure Stream Analytics job metrics](monitor-azure-stream-analytics-reference.md#metrics)
+* [Azure Stream Analytics metrics dimensions](monitor-azure-stream-analytics-reference.md#metric-dimensions)

articles/stream-analytics/includes/metrics-dimensions.md

@@ -12,8 +12,6 @@ ms.custom: "include file"
 
 
 
-Stream Analytics has [many metrics](../stream-analytics-job-metrics.md) available to monitor a job's health. To troubleshoot performance problems with your job, you can split and filter metrics by using the following dimensions. 
-
 | Dimension                 | Definition                               | 
 | ---------------------- | ---------------------------------------- | 
 | **Logical Name**       | The input or output name for a Stream Analytics job. |

articles/stream-analytics/job-diagram-with-metrics.md

@@ -15,7 +15,7 @@ The job diagram in the Azure portal can help you visualize your job's query step
 
 There are two types of job diagrams: 
 
-* **Physical diagram**: it visualizes the key metrics of Stream Analytics job with the physical computation concept: streaming node dimension. A streaming node represents a set of compute resources that's used to process job's input data. To learn more details about the streaming node dimension, see [Azure Stream Analytics node name dimension](./stream-analytics-job-metrics-dimensions.md#node-name-dimension).
+* **Physical diagram**: it visualizes the key metrics of Stream Analytics job with the physical computation concept: streaming node dimension. A streaming node represents a set of compute resources that's used to process job's input data. To learn more details about the streaming node dimension, see [Azure Stream Analytics node name dimension](monitor-azure-stream-analytics-reference.md#node-name-dimension).
 
    Inside each streaming node, there are Stream Analytics processors available for processing the stream data. Each processor represents one or more steps in your query. You can visualize the processor topology in each streaming node by using the **processor diagram** in physical job diagram.
 
@@ -59,7 +59,7 @@ The following screenshot shows a physical job diagram with a default time period
     * **Watermark Delay** (Aggregation type: Max)
     * **Backlogged Input Events** (Aggregation type: SUM)
 
-    For more information about the metrics definition, see [Azure Stream Analytics node name dimension](./stream-analytics-job-metrics-dimensions.md#node-name-dimension).
+    For more information about the metrics definition, see [Azure Stream Analytics node name dimension](monitor-azure-stream-analytics-reference.md#node-name-dimension).
 1. **Chart section**: it's the place where you can view the historical metrics data within the selected time range. The default metrics shown in the default chart are **SU (Memory) % Utilization** and **CPU % Utilization**". You can also add more charts by clicking **Add chart**.
 
 The **Diagram/Table section** and **Chart section** can be interactive with each other. You can select multiple nodes in **Diagram/Table section** to get the metrics in **Chart section** filtered by the selected nodes and vice versa.
@@ -109,7 +109,7 @@ The logical job diagram has a similar layout to the physical diagram, with three
 :::image type="content" source="./media/job-diagram-with-metrics/3-logical-diagram-overview.png" alt-text="Screenshot that shows logical job diagram sections."  lightbox="./media/job-diagram-with-metrics/3-logical-diagram-overview.png":::
 
 1. **Command bar section**: in logical diagram, you can operate the cloud job (Stop, Delete), and configure the time range of the job metrics. The diagram view is only available for logical diagrams.
-2. **Diagram section**: the node box in this selection represents the job's input, output, and query steps. You can view the metrics in the node directly or in the chart section interactively by clicking certain node in this section. For more information about the metrics definition, see [Azure Stream Analytics node name dimension](./stream-analytics-job-metrics-dimensions.md#node-name-dimension).
+2. **Diagram section**: the node box in this selection represents the job's input, output, and query steps. You can view the metrics in the node directly or in the chart section interactively by clicking certain node in this section. For more information about the metrics definition, see [Azure Stream Analytics node name dimension](monitor-azure-stream-analytics-reference.md#node-name-dimension).
 3. **Chart section**: the chart section in a logical diagram has two tabs: **Metrics** and **Activity Logs**.
     * **Metrics**: job's metrics data is shown here when the corresponding metrics are selected in the right panel. 
     * **Activity Logs**: job's operations performed on jobs is shown here. When the job's diagnostic log is enabled, it's also shown here. To learn more about the job logs, see [Azure Stream Analytics job logs](./stream-analytics-job-diagnostic-logs.md).
@@ -126,7 +126,7 @@ To learn more about how to debug with logical diagrams, see [Debugging with the
 ## Next steps
 * [Introduction to Stream Analytics](stream-analytics-introduction.md)
 * [Get started with Stream Analytics](stream-analytics-real-time-fraud-detection.md)
-* [Azure Stream Analytics job metrics](./stream-analytics-job-metrics.md)
+* [Azure Stream Analytics job metrics](monitor-azure-stream-analytics-reference.md#metrics)
 * [Scale Stream Analytics jobs](stream-analytics-scale-jobs.md)
 * [Stream Analytics query language reference](/stream-analytics-query/stream-analytics-query-language-reference)
 * [Stream Analytics management REST API reference](/rest/api/streamanalytics/)

articles/stream-analytics/job-states.md

@@ -15,12 +15,12 @@ A Stream Analytics job could be in one of four states at any given time: running
 
 | State | Description | Recommended actions |
 | --- | --- | --- |
-| **Running** | Your job is running on Azure reading events coming from the defined input sources, processing them and writing the results to the configured output sinks. | It's a best practice to track your job’s performance by monitoring [key metrics](./stream-analytics-job-metrics.md#scenarios-to-monitor). |
+| **Running** | Your job is running on Azure reading events coming from the defined input sources, processing them and writing the results to the configured output sinks. | It's a best practice to track your job’s performance by monitoring [key metrics](monitor-azure-stream-analytics.md#azure-stream-analytics-metrics). |
 | **Stopped** | Your job is stopped and doesn't process events. | NA | 
-| **Degraded** | There might be intermittent issues with your input and output connections. These errors are called transient errors that might make your job enter a Degraded state. Stream Analytics will immediately try to recover from such errors and return to a Running state (within few minutes). These errors could happen due to network issues, availability of other Azure resources, deserialization errors etc. Your job’s performance may be impacted when job is in degraded state.| You can look at the [diagnostic or activity logs](./stream-analytics-job-diagnostic-logs.md#debugging-using-activity-logs) to learn more about the cause of these transient errors. In cases such as deserialization errors, it's recommended to take corrective action to ensure events aren't malformed. If the job keeps reaching the resource utilization limit, try to increase the SU number or [parallelize your job](./stream-analytics-parallelization.md). In other cases where you can't take any action, Stream Analytics will try to recover to a *Running* state. <br> You can use [watermark delay](./stream-analytics-job-metrics.md#scenarios-to-monitor) metric to understand if these transient errors are impacting your job's performance.|
+| **Degraded** | There might be intermittent issues with your input and output connections. These errors are called transient errors that might make your job enter a Degraded state. Stream Analytics will immediately try to recover from such errors and return to a Running state (within few minutes). These errors could happen due to network issues, availability of other Azure resources, deserialization errors etc. Your job’s performance may be impacted when job is in degraded state.| You can look at the [diagnostic or activity logs](./stream-analytics-job-diagnostic-logs.md#debugging-using-activity-logs) to learn more about the cause of these transient errors. In cases such as deserialization errors, it's recommended to take corrective action to ensure events aren't malformed. If the job keeps reaching the resource utilization limit, try to increase the SU number or [parallelize your job](./stream-analytics-parallelization.md). In other cases where you can't take any action, Stream Analytics will try to recover to a *Running* state. <br> You can use [watermark delay](monitor-azure-stream-analytics.md#azure-stream-analytics-metrics) metric to understand if these transient errors are impacting your job's performance.|
 | **Failed** | Your job encountered a critical error resulting in a failed state. Events aren't read and processed. Runtime errors are a common cause for jobs ending up in a failed state. | You can [configure alerts](./stream-analytics-set-up-alerts.md#set-up-alerts-in-the-azure-portal) so that you get notified when job goes to Failed state. <br> <br>You can debug using [activity and resource logs](./stream-analytics-job-diagnostic-logs.md#debugging-using-activity-logs) to identify root cause and address the issue.|
 
 ## Next steps
-* [Azure Stream Analytics job metrics](./stream-analytics-job-metrics.md)
-* [Azure Stream Analytics metrics dimensions](./stream-analytics-job-metrics-dimensions.md)
+* [Azure Stream Analytics job metrics](monitor-azure-stream-analytics-reference.md#metrics)
+* [Azure Stream Analytics metrics dimensions](monitor-azure-stream-analytics-reference.md#metric-dimensions)
 * [Troubleshoot using activity and resource logs](./stream-analytics-job-diagnostic-logs.md)

articles/stream-analytics/monitor-azure-stream-analytics-reference.md

@@ -17,10 +17,18 @@ See [Monitor Azure Stream Analytics](monitor-azure-stream-analytics.md) for deta
 
 [!INCLUDE [horz-monitor-ref-metrics-intro](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-intro.md)]
 
+Azure Stream Analytics provides plenty of metrics that you can use to monitor and troubleshoot your query and job performance. You can view data from these metrics on the **Overview** page of the Azure portal, in the **Monitoring** section.  
+
+:::image type="content" source="./media/stream-analytics-job-metrics/02-stream-analytics-job-metrics-monitoring-block.png" alt-text="Screenshot of the Azure portal that shows the section for monitoring Stream Analytics jobs." lightbox="./media/stream-analytics-job-metrics/02-stream-analytics-job-metrics-monitoring-block.png":::
+
+If you want to check a specific metric, select **Metrics** in the **Monitoring** section. On the page that appears, select the metric.
+
+:::image type="content" source="./media/stream-analytics-job-metrics/01-stream-analytics-job-metrics-monitoring.png" alt-text="Screenshot that shows selecting a metric in the Stream Analytics job monitoring dashboard." lightbox="./media/stream-analytics-job-metrics/01-stream-analytics-job-metrics-monitoring.png":::
+
 ### Supported metrics for Microsoft.StreamAnalytics/streamingjobs
 The following table lists the metrics available for the Microsoft.StreamAnalytics/streamingjobs resource type.
 [!INCLUDE [horz-monitor-ref-metrics-tableheader](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-tableheader.md)]
-[!INCLUDE [Microsoft.StreamAnalytics/streamingjobs](~/azure-reference-other-repo/azure-monitor-ref/supported-metrics/includes/microsoft-streamanalytics-streamingjobs-metrics-include.md)]
+[!INCLUDE [microsoft-streamanalytics-streamingjobs-metrics-include](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/metrics/microsoft-streamanalytics-streamingjobs-metrics-include.md)]
 
 ### Metrics descriptions
 
@@ -30,27 +38,31 @@ The following table lists the metrics available for the Microsoft.StreamAnalytic
 
 [!INCLUDE [horz-monitor-ref-metrics-dimensions](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions.md)]
 
-- **Logical Name**: The input or output name for an Azure Stream Analytics job.
-- **Partition ID**: The ID of the input data partition from an input source.
-- **Node Name**: The identifier of a streaming node that's provisioned when a job runs.
+[!INCLUDE [metrics-dimensions](./includes/metrics-dimensions.md)]
+
+### Logical Name dimension
 
-For detailed information, see [Dimensions for Azure Stream Analytics metrics](stream-analytics-job-metrics-dimensions.md).
+[!INCLUDE [metrics-dimension-logical-name](./includes/metrics-dimension-logical-name.md)]
+
+### Node Name dimension
+
+[!INCLUDE [metrics-dimension-node-name](./includes/metrics-dimension-node-name.md)]
+
+### Partition ID dimension
+
+[!INCLUDE [metrics-partition-id](./includes/metrics-dimension-partition-id.md)]
 
 [!INCLUDE [horz-monitor-ref-resource-logs](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-resource-logs.md)]
 
 ### Supported resource logs for Microsoft.StreamAnalytics/streamingjobs
-[!INCLUDE [Microsoft.StreamAnalytics/streamingjobs](~/azure-reference-other-repo/azure-monitor-ref/supported-logs/includes/microsoft-streamanalytics-streamingjobs-logs-include.md)]
+[!INCLUDE [microsoft-streamanalytics-streamingjobs-logs-include](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/logs/microsoft-streamanalytics-streamingjobs-logs-include.md)]
 
 For the resource logs schema and properties for data errors and events, see [Resource logs schema](stream-analytics-job-diagnostic-logs.md#resource-logs-schema).
 
 [!INCLUDE [horz-monitor-ref-logs-tables](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-logs-tables.md)]
 
 ### Stream Analytics jobs
-microsoft.streamanalytics/streamingjobs
-
-- [AzureActivity](/azure/azure-monitor/reference/tables/AzureActivity)
-- [AzureMetrics](/azure/azure-monitor/reference/tables/AzureMetrics)
-- [AzureDiagnostics](/azure/azure-monitor/reference/tables/AzureDiagnostics)
+[!INCLUDE [microsoft-streamanalytics-streamingjobs-logs-include](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/logs/microsoft-streamanalytics-streamingjobs-logs-include.md)]
 
 [!INCLUDE [horz-monitor-ref-activity-log](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-activity-log.md)]
 - [Microsoft.StreamAnalytics resource provider operations](../role-based-access-control/permissions/internet-of-things.md#microsoftstreamanalytics)
@@ -59,5 +71,5 @@ microsoft.streamanalytics/streamingjobs
 
 - [Monitor Azure resources with Azure Monitor](../azure-monitor/essentials/monitor-azure-resource.md)
 - [Monitor Azure Stream Analytics](monitor-azure-stream-analytics.md)
-- [Dimensions for Azure Stream Analytics metrics](stream-analytics-job-metrics-dimensions.md)
+- [Dimensions for Azure Stream Analytics metrics](monitor-azure-stream-analytics-reference.md#metric-dimensions)
 - [Understand and adjust streaming units](stream-analytics-streaming-unit-consumption.md)

articles/stream-analytics/no-code-stream-processing.md

@@ -19,7 +19,7 @@ With the no-code editor, you can easily:
 - Perform data preparation operations like joins and filters.
 - Approach advanced scenarios like time-window aggregations (tumbling, hopping, and session windows) for group-by operations.
 
-After you create and run your Stream Analytics jobs, you can easily operationalize production workloads. Use the right set of [built-in metrics](stream-analytics-job-metrics.md) for monitoring and troubleshooting purposes. Stream Analytics jobs are billed according to the [pricing model](https://azure.microsoft.com/pricing/details/stream-analytics/) when they're running.
+After you create and run your Stream Analytics jobs, you can easily operationalize production workloads. Use the right set of [built-in metrics](monitor-azure-stream-analytics-reference.md#metrics) for monitoring and troubleshooting purposes. Stream Analytics jobs are billed according to the [pricing model](https://azure.microsoft.com/pricing/details/stream-analytics/) when they're running.
 
 ## Prerequisites
 
@@ -410,7 +410,7 @@ If the job is running, you can monitor the health of your job on the **Metrics**
 
 :::image type="content" source="./media/no-code-stream-processing/metrics-nocode.png" alt-text="Screenshot that shows the metrics for a job created from the no-code editor." lightbox= "./media/no-code-stream-processing/metrics-nocode.png" :::
 
-You can select more metrics from the list. To understand all the metrics in detail, see [Azure Stream Analytics job metrics](stream-analytics-job-metrics.md).
+You can select more metrics from the list. To understand all the metrics in detail, see [Azure Stream Analytics job metrics](monitor-azure-stream-analytics-reference.md#metrics).
 
 ## Start a Stream Analytics job
 
@@ -447,7 +447,7 @@ These are the elements of the **Stream Analytics jobs** tab:
 - **Status**: This area shows the status of the job. Select **Refresh** on top of the list to see the latest status.
 - **Streaming units**: This area shows the number of streaming units that you selected when you started the job.
 - **Output watermark**: This area provides an indicator of liveliness for the data that the job has produced. All events before the time stamp are already computed.
-- **Job monitoring**: Select **Open metrics** to see the metrics related to this Stream Analytics job. For more information about the metrics that you can use to monitor your Stream Analytics job, see [Azure Stream Analytics job metrics](./stream-analytics-job-metrics.md).
+- **Job monitoring**: Select **Open metrics** to see the metrics related to this Stream Analytics job. For more information about the metrics that you can use to monitor your Stream Analytics job, see [Azure Stream Analytics job metrics](monitor-azure-stream-analytics-reference.md#metrics).
 - **Operations**: Start, stop, or delete the job.
 
 ## Next steps