Merge pull request #279819 from cdpark/horz-monitor-streamanalytics

Q&M: Curate 27 SOX Azure Monitor horizontals articles to reduce duplication - Stream Analytics

Author: v-dirichards

.openpublishing.redirection.json

@@ -3702,6 +3702,16 @@
             "redirect_url": "/sql/sql-server/stretch-database/stretch-database-databases-and-tables-stretch-database-advisor",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/stream-analytics/stream-analytics-job-metrics.md",
+            "redirect_url": "/azure/stream-analytics/monitor-azure-stream-analytics-reference#metrics",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/stream-analytics/stream-analytics-job-metrics-dimensions.md",
+            "redirect_url": "/azure/stream-analytics/monitor-azure-stream-analytics-reference#metric-dimensions",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/dms/tutorial-azure-postgresql-to-azure-postgresql-online-portal.md",
             "redirect_url": "/azure/postgresql/migrate/migration-service/tutorial-migration-service-single-to-flexible",

articles/stream-analytics/TOC.yml

@@ -85,12 +85,6 @@
       href: ./security-controls-policy.md
     - name: Security baseline
       href: /security/benchmark/azure/baselines/stream-analytics-security-baseline?toc=/azure/stream-analytics/TOC.json
-  - name: Metrics for job monitoring
-    items:
-    - name: Stream Analytics metrics
-      href: stream-analytics-job-metrics.md
-    - name: Stream Analytics metrics dimensions
-      href: stream-analytics-job-metrics-dimensions.md
   - name: Integrate with Schema Registry
     href: stream-analytics-schema-registry-integration.md
   - name: Input types for a job
@@ -323,7 +317,7 @@
       href: geospatial-scenarios.md
   - name: Monitor
     items:
-    - name: Monitor Azure Stream Analytics
+    - name: Monitor Stream Analytics
       href: monitor-azure-stream-analytics.md
     - name: Monitoring data reference
       href: monitor-azure-stream-analytics-reference.md

articles/stream-analytics/cicd-autoscale.md

@@ -87,27 +87,9 @@ If you have a working Stream Analytics project on the local machine, follow thes
 
     ![Screenshot that shows autoscale files generated after configuration of autoscale.](./media/cicd-autoscale/configure-autoscale.png)
 
-    Here's the list of metrics that you can use to define autoscale rules:
-
-    |Metric                        | Description           |
-    |------------------------------|-------------------|
-    |`ProcessCPUUsagePercentage`      | CPU utilization percentage |
-    |`ResourceUtilization`            | SU or memory utilization percentage |
-    |`OutputWatermarkDelaySeconds`    | Watermark delay |
-    |`InputEventsSourcesBacklogged`   | Backlogged input events |
-    |`DroppedOrAdjustedEvents`        | Out-of-order events |
-    |`Errors`                         | Runtime errors |
-    |`InputEventBytes`                | Input event bytes |
-    |`LateInputEvents`                | Late input events |
-    |`InputEvents`                    | Input events |
-    |`EarlyInputEvents`               | Early input events |
-    |`InputEventsSourcesPerSecond`    | Input sources received |
-    |`OutputEvents`                   | Output events |
-    |`AMLCalloutRequests`             | Function requests |
-    |`AMLCalloutFailedRequests`       | Failed function requests |
-    |`AMLCalloutInputEvents`          | Function events |
-    |`ConversionErrors`               | Data conversion errors |
-    |`DeserializationError`           | Input deserialization error |
+    The following table lists the metrics that you can use to define autoscale rules:
+
+    [!INCLUDE [microsoft-streamanalytics-streamingjobs-metrics-include](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/metrics/microsoft-streamanalytics-streamingjobs-metrics-include.md)]
 
     The default value for all metric thresholds is `70`. If you want to set the metric threshold to another number, open the *\*.AutoscaleSettingTemplate.parameters.json* file and change the `Threshold` value. 
 

articles/stream-analytics/data-errors.md

@@ -16,7 +16,7 @@ This article outlines the different error types, causes, and resource log detail
 
 ## Resource Logs schema
 
-See [Troubleshoot Azure Stream Analytics by using diagnostics logs](stream-analytics-job-diagnostic-logs.md#resource-logs-schema) to see the schema for resource logs. The following JSON is an example value for the **Properties** field of a resource log for a data error.
+See [Troubleshoot Azure Stream Analytics by using diagnostics logs](monitor-azure-stream-analytics-reference.md#resource-logs-schema) to see the schema for resource logs. The following JSON is an example value for the **Properties** field of a resource log for a data error.
 
 ```json
 {

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/index.yml

@@ -86,12 +86,6 @@ landingContent:
             url: stream-analytics-troubleshoot-output.md
   - title: Monitor and troubleshoot your job
     linkLists: 
-      - linkListType: concept
-        links:
-          - text: Stream Analytics job metrics 
-            url: stream-analytics-job-metrics.md
-          - text: Stream Analytics dimensions for job metrics
-            url: stream-analytics-job-metrics-dimensions.md
       - linkListType: how-to-guide
         links:
           - text: Monitor and manage jobs using Azure portal

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)