Merge pull request #113393 from sidramadoss/patch-68

Update stream-analytics-monitoring.md

Author: PRMerger7

articles/stream-analytics/copy-job.md

@@ -11,7 +11,7 @@ ms.date: 09/11/2019
 
 # Copy or back up Azure Stream Analytics jobs
 
-You can copy or back up your deployed Azure Stream Analytics jobs using Visual Studio Code or Visual Studio. 
+You can copy or back up your deployed Azure Stream Analytics jobs using Visual Studio Code or Visual Studio. Copying a job to another region does not copy the last output time. Therefore, you cannot use [**When last stopped**](https://docs.microsoft.com/azure/stream-analytics/start-job#start-options) option when starting the copied job.
 
 ## Before you begin
 * If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/).

articles/stream-analytics/custom-deserializer-examples.md

@@ -243,6 +243,10 @@ This functionality is not supported. If you need this capability, you can vote f
 
 Once you have implemented your deserializer, you can help others by sharing it with the community. Submit your code to the [Azure Stream Analytics GitHub repo](https://github.com/Azure/azure-stream-analytics/tree/master/CustomDeserializers).
 
+### What are the other limitation of using custom deserializers in Stream Analytics?
+
+If your input is of Protobuf format with schema containing MapField type, you will not be able to implement a custom deserializer. We are working on supporting this type going forward.
+
 ## Next Steps
 
 * [.NET custom deserializers for Azure Stream Analytics cloud jobs](custom-deserializer.md)

articles/stream-analytics/stream-analytics-monitoring.md

@@ -31,7 +31,7 @@ The window will appear as shown:
 | Function Requests      | Number of calls to the Azure Machine Learning function (if present). |
 | Input Deserialization Errors       | Number of input events that could not be deserialized.  |
 | Input Event Bytes      | Amount of data received by the Stream Analytics job, in bytes. This can be used to validate that events are being sent to the input source. |
-| Input Events           | Number of records deserialized from the input events. This count does not include incoming events that result in deserialization errors. |
+| Input Events           | Number of records deserialized from the input events. This count does not include incoming events that result in deserialization errors. The same events can be ingested by Stream Analytics multiple times in scenarios such as internal recoveries and self joins. Therefore it is recommended not to expect Input Events and Output Events metrics to match if your job has a simple 'pass through' query. |
 | Input Sources Received       | Number of messages received by the job. For Event Hub, a message is a single EventData. For Blob, a message is a single blob. Please note that Input Sources are counted before deserialization. If there are deserialization errors, input sources can be greater than input events. Otherwise, it can be less than or equal to input events since each message can contain multiple events. |
 | Late Input Events      | Events that arrived later than the configured late arrival tolerance window. Learn more about [Azure Stream Analytics event order considerations](stream-analytics-out-of-order-and-late-events.md) . |
 | Out-of-Order Events    | Number of events received out of order that were either dropped or given an adjusted timestamp, based on the Event Ordering Policy. This can be impacted by the configuration of the Out of Order Tolerance Window setting. |