Merge branch 'MicrosoftDocs:main' into docs-editor/container-insights-onboard-1695680784

Author: bwren

articles/aks/learn/quick-kubernetes-deploy-terraform.md

@@ -36,6 +36,10 @@ In this article, you learn how to:
 
 - **Kubernetes command-line tool (kubectl):** [Download kubectl](https://kubernetes.io/releases/download/).
 
+## Login to your Azure Account
+
+[!INCLUDE [authenticate-to-azure.md](~/azure-dev-docs-pr/articles/terraform/includes/authenticate-to-azure.md)]
+
 ## Implement the Terraform code
 
 > [!NOTE]

articles/azure-functions/TOC.yml

@@ -543,6 +543,8 @@
           href: migrate-version-3-version-4.md
         - name: Migrate v1.x to v4.x
           href: migrate-version-1-version-4.md
+        - name: Update Java versions
+          href: update-java-versions.md  
     - name: Monitor
       items:
         - name: Monitor function apps with Azure Monitor

articles/azure-functions/media/update-java-versions/update-functions-version-portal.png

@@ -0,0 +1,107 @@
+---
+title: Update Java versions in Azure Functions
+description: Learn how to update an existing function app in Azure Functions to run on a new version of Java.
+ms.topic: how-to
+ms.date: 09/14/2023
+zone_pivot_groups: app-service-platform-windows-linux
+---
+
+# Update Java versions in Azure Functions 
+
+The Azure Functions supports specific versions of Java. This support changes based on the support or Java versions. As these supported versions change, you need to update your Java function apps. You may also want to update your apps to take advantage of features in newer supported version of Java. For more information, see [Supported versions](functions-reference-java.md#supported-versions) in the Java developer guide.   
+
+:::zone pivot="platform-windows"  
+The way that you update your function app depends on whether you run on Windows or Linux. This version is for Windows. Choose your OS at the [top](#top) of the article.  
+:::zone-end  
+:::zone pivot="platform-linux"  
+The way that you update your function app depends on whether you run on Windows or Linux. This version is for Linux. Choose your OS at the [top](#top) of the article.  
+:::zone-end  
+
+## Prepare to update
+
+Before you update the Java version in Azure, you should complete these tasks:
+
+### 1. Verify your functions locally
+
+Before upgrading the Java version used by your function app in Azure, make sure that you have fully tested and verified your function code locally on the new target version of Java. Examples in this article assume you're updating to Java 17. 
+
+### 2. Move to the latest Functions runtime
+ 
+Before updating your Java version, make sure your function app is running on the latest version of the Functions runtime (version 4.x). 
+
+### [Azure portal](#tab/azure-portal)
+
+Use these steps to determine your Functions runtime version:
+
+1. In the [Azure portal](https://portal.azure.com), locate your function app and select **Configuration** on the left-hand side under **Settings**. 
+
+1. Select the **Function runtime settings** tab and check the **Runtime version** value to see if your function app is running on version 4.x of the Functions runtime (`~4`). 
+
+    :::image type="content" source="media/update-java-versions/update-functions-version-portal.png" alt-text="Screenshot of how to view the Functions runtime version for your app in the Azure portal."::: 
+
+### [Azure CLI](#tab/azure-cli)
+
+Use this [`az functionapp config appsettings list`](/cli/azure/functionapp/config/appsettings#az-functionapp-config-appsettings-list) command to check your runtime version: 
+
+```azurecli
+az functionapp config appsettings list --name "<FUNCTION_APP_NAME>" --resource-group "<RESOURCE_GROUP_NAME>"  
+```
+The `FUNCTIONS_EXTENSION_VERSION` setting sets the runtime version. A value of `~4` means that your function app is already running on the latest minor version of the latest major version (4.x). 
+
+---
+
+If you need to first update your function app to version 4.x, see [Migrate apps from Azure Functions version 3.x to version 4.x](./migrate-version-3-version-4.md). You should follow the instructions in this article rather than just manually changing the `FUNCTIONS_EXTENSION_VERSION` setting.
+
+## Update the Java version
+:::zone pivot="platform-windows"  
+You can use the Azure portal, Azure CLI, or Azure PowerShell to update the Java version for your function app. 
+These procedures apply to all [Functions hosting options](./functions-scale.md). 
+:::zone-end  
+:::zone pivot="platform-linux"  
+>[!NOTE] 
+> You can't change the Java version in the Azure portal when your function app is running on Linux in a [Consumption plan](./consumption-plan.md). Instead use the Azure CLI. 
+:::zone-end  
+### [Azure portal](#tab/azure-portal)
+:::zone pivot="platform-linux" 
+You can only use these steps for function apps hosted in a [Premium plan](./functions-premium-plan.md) or a [Dedicated (App Service) plan](./dedicated-plan.md). For a [Consumption plan](./consumption-plan.md), you must instead use the Azure CLI.
+::: zone-end  
+Use the following steps to update the Java version: 
+
+1. In the [Azure portal](https://portal.azure.com), locate your function app and select **Configuration** on the left-hand side. 
+
+1. In the **General settings** tab, update the **Java version** to `Java 17`. 
+
+    :::image type="content" source="media/update-java-versions/update-java-version-portal.png" alt-text="Screenshot of how to set the desired Java version for a function app in the Azure portal."::: 
+
+1. When notified about a restart, select **Continue**, and then **Save**. 
+
+### [Azure CLI](#tab/azure-cli)
+
+You can use the Azure CLI to update the Java version for any hosting plan.
+
+:::zone pivot="platform-windows"  
+Run the [`az functionapp config set`](/cli/azure/functionapp/config#az-functionapp-config-set) command to update the Java version site setting to `17`: 
+
+```azurecli
+az functionapp config set --java-version "17" --name "<APP_NAME>" --resource-group "<RESOURCE_GROUP>" 
+```
+:::zone-end  
+:::zone pivot="platform-linux"   
+Run the [`az functionapp config set`](/cli/azure/functionapp/config#az-functionapp-config-set) command to update the Linux site setting with the new Java version for your function app. 
+
+```azurecli
+az functionapp config set --linux-fx-version "java|17" --name "<APP_NAME>" --resource-group "<RESOURCE_GROUP>" 
+```
+:::zone-end  
+
+In this example, replace `<APP_NAME>` and `<RESOURCE_GROUP>` with the name of your function app and resource group, respectively.  
+
+---
+
+Your function app restarts after you update the Java version. To learn more about Functions support for Java, see [Language runtime support policy](language-support-policy.md). 
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Java developer guide](./functions-reference-java.md)
+ 

articles/azure-functions/media/update-java-versions/update-java-version-portal.png

@@ -10,15 +10,15 @@ ms.reviewer: mmcc
 
 # Enable Azure Monitor Application Insights Real User Monitoring
 
-The Microsoft Azure Monitor Application Insights JavaScript SDK collects usage data which allows you to monitor and analyze the performance of JavaScript web applications. This is commonly referred to as Real User Monitoring or RUM.
+The Microsoft Azure Monitor Application Insights JavaScript SDK collects usage data, which allows you to monitor and analyze the performance of JavaScript web applications. This is commonly referred to as Real User Monitoring or RUM.
 
-The Application Insights JavaScript SDK has a base SDK and several plugins for additional capabilities.
+The Application Insights JavaScript SDK has a base SDK and several plugins for more capabilities.
 
 :::image type="content" source="media/javascript-sdk/conceptual-diagram-javascript-sdk.png" alt-text="Conceptual diagram that shows the Application Insights JavaScript SDK, its plugins/extensions, and their relationship to each other." lightbox="media/javascript-sdk/conceptual-diagram-javascript-sdk.png":::
 
 We collect page views by default. But if you want to also collect clicks by default, consider adding the [Click Analytics Auto-Collection plug-in](./javascript-feature-extensions.md): 
 
-- If you're adding a [framework extension](./javascript-framework-extensions.md), which you can [add](#optional-add-advanced-sdk-configuration) after you follow the steps to get started below, you'll have the option to add Click Analytics when you add the framework extension. 
+- If you're adding a [framework extension](./javascript-framework-extensions.md), which you can [add](#optional-add-advanced-sdk-configuration) after you follow the steps to get started below, you can optionally add Click Analytics when you add the framework extension. 
 - If you're not adding a framework extension, [add the Click Analytics plug-in](./javascript-feature-extensions.md) after you follow the steps to get started.
 
 We provide the [Debug plugin](https://github.com/microsoft/ApplicationInsights-JS/blob/main/extensions/applicationinsights-debugplugin-js/README.md) and [Performance plugin](https://github.com/microsoft/ApplicationInsights-JS/blob/main/extensions/applicationinsights-perfmarkmeasure-js/README.md) for debugging/testing. In rare cases, it's possible to build your own extension by adding a [custom plugin](https://github.com/microsoft/ApplicationInsights-JS/blob/e4be62c0aa9318b540157118b729bb0c4d8b6c6e/API-reference.md#custom-extension).
@@ -62,6 +62,7 @@ Two methods are available to add the code to enable Application Insights via the
    // useXhr: 1,
    crossOrigin: "anonymous",
    // onInit: null,
+   // cr: 0,
    cfg: { // Application Insights Configuration
     connectionString: "YOUR_CONNECTION_STRING"
    }});
@@ -82,6 +83,7 @@ Two methods are available to add the code to enable Application Insights via the
    | useXhr | boolean | Optional | This setting is used only for reporting SDK load failures. For example, this setting is useful when the JavaScript (Web) SDK Loader Script is preventing the HTML page from loading, causing fetch() to be unavailable.<br><br>Reporting first attempts to use fetch() if available and then fallback to XHR. Set this setting to `true` to bypass the fetch check. This setting is only required if your application is being used in an environment where fetch would fail to send the failure events such as if the JavaScript (Web) SDK Loader Script isn't loading successfully.
    | crossOrigin | string  | Optional | By including this setting, the script tag added to download the SDK includes the crossOrigin attribute with this string value. Use this setting when you need to provide support for CORS. When not defined (the default), no crossOrigin attribute is added. Recommended values are not defined (the default), "", or "anonymous". For all valid values, see the [cross origin HTML attribute](https://developer.mozilla.org/docs/Web/HTML/Attributes/crossorigin) documentation.
    | onInit | function(aiSdk) { ... } | Optional | This callback function is called after the main SDK script has been successfully loaded and initialized from the CDN (based on the src value). This callback function is useful when you need to insert a telemetry initializer. It's passed one argument, which is a reference to the SDK instance that's being called for and is also called before the first initial page view. If the SDK has already been loaded and initialized, this callback is still called. NOTE: During the processing of the sdk.queue array, this callback is called. You CANNOT add any more items to the queue because they're ignored and dropped. (Added as part of JavaScript (Web) SDK Loader Script version 5--the sv:"5" value within the script). |
+   | cr | boolean | Optional | If the SDK fails to load and the endpoint value defined for `src` is the public CDN location, this configuration option attempts to immediately load the SDK from one of the following backup CDN endpoints:<ul><li>js.monitor.azure.com</li><li>js.cdn.applicationinsights.io</li><li>js.cdn.monitor.azure.com</li><li>js0.cdn.applicationinsights.io</li><li>js0.cdn.monitor.azure.com</li><li>js2.cdn.applicationinsights.io</li><li>js2.cdn.monitor.azure.com</li><li>az416426.vo.msecnd.net</li></ul>NOTE: az416426.vo.msecnd.net is partially supported, so it's not recommended.<br><br>If the SDK successfully loads from a backup CDN endpoint, it loads from the first available one, which is determined when the server performs a successful load check. If the SDK fails to load from any of the backup CDN endpoints, the SDK Failure error message appears.<br><br>When not defined, the default value is `true`. If you don’t want to load the SDK from the backup CDN endpoints, set this configuration option to `false`.<br><br>If you’re loading the SDK from your own privately hosted CDN endpoint, this configuration option is not applicable.
 
 #### [npm package](#tab/npmpackage)
 

articles/azure-functions/update-java-versions.md

@@ -38,6 +38,8 @@
     href: chaos-studio-faults-actions.md
   - name: Targets and capabilities
     href: chaos-studio-targets-capabilities.md
+  - name: Target selection
+    href: chaos-studio-target-selection.md
   - name: Permissions and security
     href: chaos-studio-permissions-security.md
   - name: Private networking

articles/azure-monitor/app/javascript-sdk.md

@@ -0,0 +1,33 @@
+---
+title: Target selection in Azure Chaos Studio Preview
+description: Understand two different ways to select experiment targets in Azure Chaos Studio Preview.
+author: prasha-microsoft
+ms.author: prashabora
+ms.service: chaos-studio
+ms.topic: conceptual
+ms.date: 09/25/2023
+ms.custom: template-concept, ignite-fall-2021, devx-track-arm-template
+---
+
+# Target selection in Azure Chaos Studio Preview
+
+Every chaos experiment is made up of a different combination of faults and targets, building up to a unique outage scenario to test your system's resilience against. You may want to select a fixed set of targets for your chaos experiment, or provide a rule in which all matching fault-onboarded resources are included as targets in your experiment. Chaos Studio enables you to do both by providing both manual and query-based target selection.
+
+## List-based manual target selection
+
+List-based manual target selection allows you to select a fixed set of onboarded targets for a particular fault in your chaos experiment. Depending on the selected fault, you may select one or more onboarded resources to target. The aforementioned resources are added to the experiment upon creation time. In order to modify the list, you must navigate to the experiment's page and add or remove fault targets manually. An example of manual target selection is shown below.
+
+[ ![Screenshot that shows the list-based manual target selection option in the Azure portal.](images/manual-target-selection.png) ](images/manual-target-selection.png#lightbox)
+
+## Query-based dynamic target selection
+
+Query-based dynamic target selection allows you to input a KQL query that will select all onboarded targets that match the query result set. Using your query, you may filter targets based on common Azure resource parameters including type, region, name, and more. Upon experiment creation time, only the query itself will be added to your chaos experiment. 
+
+The inputted query will run and add onboarded targets that match its result set upon experiment execution time. Thus, any resources onboarded to Chaos Studio after experiment creation time that match the query result set upon experiment execution time will be targeted by your experiment. You may preview your query's result set when adding it to your experiment, but be aware that it may not match the result set at experiment execution time. An example of a possible dynamic target query is shown below.
+
+[ ![Screenshot that shows the query-based dynamic target selection option in the Azure portal.](images/dynamic-target-selection-preview.png) ](images/dynamic-target-selection-preview.png#lightbox)
+
+## Next steps
+Now that you understand both ways to select targets within a chaos experiment, you're ready to:
+
+- [Create and run your first experiment](chaos-studio-tutorial-service-direct-portal.md)