Merge branch 'master' of https://github.com/Microsoft/azure-docs-pr into clusterupgrade

Author: rwike77

articles/application-insights/app-insights-performance-counters.md

@@ -92,7 +92,7 @@ Or you can do the same thing with custom metrics you created:
 ## Performance counters in Analytics
 You can search and display performance counter reports in [Analytics](app-insights-analytics.md).
 
-The **performanceCounters** schema exposes the `category`, `counter` name, and `instance` name of each performance counter.  In the telemetry for each application, you’ll see only the counters for that application. For example, to see what counters are available: 
+The **performanceCounters** schema exposes the `category`, `counter` name, and `instance` name of each performance counter.  In the telemetry for each application, you'll see only the counters for that application. For example, to see what counters are available: 
 
 ![Performance counters in Application Insights analytics](./media/app-insights-performance-counters/analytics-performance-counters.png)
 

articles/azure-monitor/insights/vminsights-onboard.md

@@ -691,6 +691,8 @@
           href: ../log-analytics/query-language/advanced-query-writing.md?toc=/azure/azure-monitor/toc.json
         - name: Charts and diagrams
           href: ../log-analytics/query-language/charts.md?toc=/azure/azure-monitor/toc.json
+        - name: Functions
+          href: ../log-analytics/query-language/functions.md?toc=/azure/azure-monitor/toc.json
       - name: Cheatsheets
         items:
         - name: SQL

articles/azure-monitor/toc.yml

@@ -14,7 +14,10 @@ ms.author: v-jansko
 
 # Translator Text API V2 to V3 Migration
 
-The Microsoft Translator team has released Version 3 (V3) of the Translator Text API. This release includes new features, deprecated methods and a new format for sending to, and receiving data from the Microsoft Translator Service. This document provides information for changing applications to use V3. V2 will be deprecated on April 30, 2018 and will be discontinued on April 30, 2019.
+> [!NOTE]
+> V2 was deprecated on April 30, 2018 and will be discontinued on April 30, 2019.
+
+The Microsoft Translator team has released Version 3 (V3) of the Translator Text API. This release includes new features, deprecated methods and a new format for sending to, and receiving data from the Microsoft Translator Service. This document provides information for changing applications to use V3. 
 
 The end of this document contains helpful links for you to learn more.
 

articles/cognitive-services/Translator/migrate-to-v3.md

@@ -131,6 +131,7 @@ The error code is a 6-digit number combining the 3-digit HTTP status code follow
 | 403000| The operation is not allowed.|
 | 403001| The operation is not allowed because the subscription has exceeded its free quota.|
 | 405000| The request method is not supported for the requested resource.|
+| 408001| The custom translation system requested is not yet available. Please retry in a few minutes.|
 | 415000| The Content-Type header is missing or invalid.|
 | 429000, 429001, 429002| The server rejected the request because the client is sending too many requests. Reduce the frequency of requests to avoid throttling.|
 | 500000| An unexpected error occurred. If the error persists, report it with date/time of error, request identifier from response header X-RequestId, and client identifier from request header X-ClientTraceId.|

articles/cognitive-services/Translator/reference/v3-0-reference.md

@@ -80,6 +80,11 @@ Request parameters passed on the query string are:
     <td>toScript</td>
     <td>*Optional parameter*.<br/>Specifies the script of the translated text.</td>
   </tr>
+  <tr>
+    <td>AllowFallback</td>
+    <td>*Optional parameter*.<br/>Specifies that the service is allowed to fallback to a general system when a custom system does not exist. Possible values are: `true` (default) or `false`.<br/><br/>`AllowFallback=false` specifies that the translation should only use systems trained for the `category` specified by the request. If a translation for language X to language Y requires chaining through a pivot language E, then all the systems in the chain (X->E and E->Y) will need to be custom and have the same category. If no system is found with the specific category, the request will return a 400 status code. `AllowFallback=true` specifies that the service is allowed to fallback to a general system when a custom system does not exist.
+</td>
+  </tr>
 </table> 
 
 Request headers include:
@@ -103,6 +108,11 @@ Request headers include:
     <td>X-ClientTraceId</td>
     <td>*Optional*.<br/>A client-generated GUID to uniquely identify the request. You can omit this header if you include the trace ID in the query string using a query parameter named `ClientTraceId`.</td>
   </tr>
+  <tr>
+    <td>X-MT-System</td>
+    <td>*Optional*.<br/>Specifies the system type that was used for translation for each ‘to’ language requested for translation. The value is a comma-separated list of strings. Each string indicates a type:<br/><ul><li>Custom -  Request includes a custom system and at least one custom system was used during translation.</li><li>Team - All other requests</li></ul>
+</td>
+  </tr>
 </table> 
 
 ## Request body
@@ -183,6 +193,10 @@ The following are the possible HTTP status codes that a request returns.
     <td>403</td>
     <td>The request is not authorized. Check the details error message. This often indicates that all free translations provided with a trial subscription have been used up.</td>
   </tr>
+  <tr>
+    <td>408</td>
+    <td>The request could not be fulfilled because a resource is missing. Check the details error message. When using a custom `category`, this often indicates that the custom translation system is not yet available to serve requests. The request should be retried after a waiting period (e.g. 10 minutes).</td>
+  </tr>
   <tr>
     <td>429</td>
     <td>The caller is sending too many requests.</td>

articles/cognitive-services/Translator/reference/v3-0-translate.md

@@ -12,7 +12,7 @@ ms.workload: na
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: conceptual
-ms.date: 04/17/2018
+ms.date: 11/15/2018
 ms.author: magoedte
 ms.component: 
 ---
@@ -86,7 +86,7 @@ Identifying an application in Application Insights can be accomplished with the
     ```
 
 ### Performing a query across multiple resources
-You can query multiple resorces from any of your resource instances, these can be workspaces and apps combined.
+You can query multiple resources from any of your resource instances, these can be workspaces and apps combined.
     
 Example for query across two workspaces:    
 
@@ -97,6 +97,36 @@ union Update, workspace("contosoretail-it").Update, workspace("b459b4u5-912x-46d
 | summarize dcount(Computer) by Classification
 ```
 
+## Using cross-resource query for multiple resources
+When using cross-resource queries to correlate data from multiple Log Analytics and Application Insights resources, the query can become complex and difficult to maintain. You should leverage [functions in Log Analytics](query-language/functions.md) to separate the query logic from the scoping of the query resources, which simplifies the query structure. The following example demonstrates how you can monitor multiple Application Insights resources and visualize the count of failed requests by application name. 
+
+Create a query like the following that references the scope of Application Insights resources. The `withsource= SourceApp` command adds a column that designates the application name that sent the log. [Save the query as function](query-language/functions.md#create-a-function) with the alias _applicationsScoping_.
+
+```Kusto
+// crossResource function that scopes my Application Insights resources
+union withsource= SourceApp
+app('Contoso-app1').requests, 
+app('Contoso-app2').requests,
+app('Contoso-app3').requests,
+app('Contoso-app4').requests,
+app('Contoso-app5').requests
+```
+
+
+
+You can now [use this function](query-language/functions.md#use-a-function) in a cross-resource query like the following. The function alias _applicationsScoping_ returns the union of the requests table from all the defined applications. The query then filters for failed requests and visualizes the trends by application. The _parse_ operator is optional in this example. It extracts the application name from _SourceApp_ property.
+
+```Kusto
+applicationsScoping 
+| where timestamp > ago(12h)
+| where success == 'False'
+| parse SourceApp with * '(' applicationName ')' * 
+| summarize count() by applicationName, bin(timestamp, 1h) 
+| sort by count_ desc 
+| render timechart
+```
+![Timechart](media/log-analytics-cross-workspace-search/chart.png)
+
 ## Next steps
 
 Review the [Log Analytics log search reference](https://docs.microsoft.com/azure/log-analytics/query-language/kusto) to view all of the query syntax options available in Log Analytics.    

articles/log-analytics/log-analytics-cross-workspace-search.md

@@ -12,7 +12,7 @@ ms.workload: na
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: conceptual
-ms.date: 08/16/2018
+ms.date: 11/15/2018
 ms.author: bwren
 ms.component: na
 ---
@@ -73,28 +73,6 @@ Event
 | project TimeGenerated, USTimeGenerated, Source, Computer, EventLevel, EventData 
 ```
 
-## Functions
-You can save a query with a function alias so it can be referenced by other queries. For example, the following standard query returns all missing security updates reported in the last day:
-
-```Kusto
-Update
-| where TimeGenerated > ago(1d) 
-| where Classification == "Security Updates" 
-| where UpdateState == "Needed"
-```
-
-You can save this query as a function and give it an alias such as _security_updates_last_day_. Then you can use it in another query to search for SQL-related needed security updates:
-
-```Kusto
-security_updates_last_day | where Title contains "SQL"
-```
-
-To save a query as a function, select the **Save** button in the portal and change **Save as** to _Function_. The function alias can contain letters, digits, or underscores but must start with a letter or an underscore.
-
-> [!NOTE]
-> Saving a function is possible in Log Analytics queries, but currently not for Application Insights queries.
-
-
 ## Print
 `print` will return a table with a single column and a single row, showing the result of a calculation. This is often used in cases where you need a simple calcuation. For example, to find the current time in PST and add a column with EST:
 

articles/log-analytics/media/log-analytics-cross-workspace-search/chart.png

@@ -0,0 +1,78 @@
+---
+title: Functions Azure Log Analytics | Microsoft Docs
+description: This article describes how to use functions to call a query from another query in Log Analytics.
+services: log-analytics
+documentationcenter: ''
+author: bwren
+manager: carmonm
+editor: ''
+ms.assetid: 
+ms.service: log-analytics
+ms.workload: na
+ms.tgt_pltfrm: na
+ms.devlang: na
+ms.topic: conceptual
+ms.date: 11/15/2018
+ms.author: bwren
+ms.component: na
+---
+
+
+# Using functions in Azure Monitor Log Analytics
+
+> [!NOTE]
+> You should complete [Get started with the Analytics portal](get-started-analytics-portal.md) and [Getting started with queries](get-started-queries.md) before completing this lesson.
+
+[!INCLUDE [log-analytics-demo-environment](../../../includes/log-analytics-demo-environment.md)]
+
+
+To use a Log Analytics query with another query you can save it as a function. This allows you to simplify complex queries by breaking them into parts and allows you to reuse common code with multiple queries.
+
+## Create a function
+
+Create a function in the Azure portal by clicking **Save** and then providing the information in the following table.
+
+| Setting | Description |
+|:---|:---|
+| Name           | Display name for the query in **Query explorer**. |
+| Save as        | Function |
+| Function Alias | Short name to use the function in other queries. May not contain spaces and must be unique. |
+| Category       | A category to organize saved queries and functions in **Query explorer**. |
+
+> [!NOTE]
+> A function in Log Analytics cannot contain another function.
+
+> [!NOTE]
+> Saving a function is possible in Log Analytics queries, but currently not for Application Insights queries.
+
+
+
+## Use a function
+Use a function by including its alias in another query. It can be used like any other table.
+
+## Example
+The following sample query returns all missing security updates reported in the last day. Save this query as a function with the alias _security_updates_last_day_. 
+
+```Kusto
+Update
+| where TimeGenerated > ago(1d) 
+| where Classification == "Security Updates" 
+| where UpdateState == "Needed"
+```
+
+Create another to search for SQL-related needed security updates.
+
+```Kusto
+security_updates_last_day | where Title contains "SQL"
+```
+
+## Next steps
+See other lessons for using the Log Analytics query language:
+
+- [String operations](string-operations.md)
+- [Date and time operations](datetime-operations.md)
+- [Aggregation functions](aggregations.md)
+- [Advanced aggregations](advanced-aggregations.md)
+- [JSON and data structures](json-data-structures.md)
+- [Joins](joins.md)
+- [Charts](charts.md)