Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into ConvLims

Author: roygara

.openpublishing.redirection.json

@@ -4162,6 +4162,21 @@
             "redirect_url": "/azure/service-fabric/service-fabric-best-practices-security",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/service-fabric/service-fabric-diagnostics-overview.md",
+            "redirect_url": "/azure/service-fabric/monitor-service-fabric",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/service-fabric/service-fabric-diagnostics-event-generation-perf.md",
+            "redirect_url": "/azure/service-fabric/monitor-service-fabric-reference#performance-metrics",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/service-fabric/service-fabric-diagnostics-event-generation-app.md",
+            "redirect_url": "/azure/service-fabric/monitor-service-fabric#application-monitoring",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/virtual-desktop/partners.md",
             "redirect_url": "https://azuremarketplace.microsoft.com/marketplace/apps?page=1&search=azure%20virtual%20desktop",

articles/ai-studio/tutorials/copilot-sdk-build-rag.md

@@ -393,7 +393,7 @@ This system is able to interpret the intent of the query "how much does it cost?
 
 If you navigate to the trace from this flow run, you see this in action. The local traces link shows in the console output before the result of the flow test run.
 
-:::image type="content" source="../media/tutorials/develop-rag-copilot-sdk/trace-for-chat-history.png" alt-text="Screenshot shows the console output for the pf flow.":::
+:::image type="content" source="../media/tutorials/develop-rag-copilot-sdk/trace-for-chat-history.png" alt-text="Screenshot shows the console output for the pf flow." lightbox="../media/tutorials/develop-rag-copilot-sdk/trace-for-chat-history.png" :::
 
 ## Clean up resources
 

articles/governance/policy/concepts/policy-for-kubernetes.md

@@ -606,6 +606,25 @@ Finally, to identify the AKS cluster version that you're using, follow the linke
 
 ### Add-on versions available per each AKS cluster version
 
+#### 1.7.0
+Introducing expansion, a shift left feature that lets you know up front whether your workload resources (Deployments, ReplicaSets, Jobs, etc.) will produce admissible pods. Expansion shouldn't change the behavior of your policies; rather, it just shifts Gatekeeper's evaluation of pod-scoped policies to occur at workload admission time rather than pod admission time. However, to perform this evaluation it must generate and evaluate a what-if pod that is based on the pod spec defined in the workload, which may have incomplete metadata. For instance, the what-if pod will not contain the proper owner references. Because of this small risk of policy behavior changing, we're introducing expansion as disabled by default. To enable expansion for a given policy definition, set `.policyRule.then.details.source` to `All`. Built-ins will be updated soon to enable parameterization of this field. If you test your policy definition and find that the what-if pod being generated for evaluation purposes is incomplete, you can also use a mutation with source `Generated` to mutate the what-if pods. For more information on this option, view the [Gatekeeper documentation](https://open-policy-agent.github.io/gatekeeper/website/docs/expansion#mutating-example).
+
+Security improvements.
+- Released July 2024
+- Kubernetes 1.27+
+- Gatekeeper 3.16.3
+
+#### 1.6.1
+Security improvements.
+- Released May 2024
+- Gatekeeper 3.14.2
+
+#### 1.5.0
+Security improvements.
+- Released May 2024
+- Kubernetes 1.27+
+- Gatekeeper 3.16.3
+
 #### 1.4.0
 
 Enables mutation and external data by default. The additional mutating webhook and increased validating webhook timeout cap might add latency to calls in the worst case. Also introduces support for viewing policy definition and set definition version in compliance results.

articles/service-fabric/monitor-service-fabric-reference.md

@@ -18,7 +18,7 @@ See [Monitor Service Fabric](monitor-service-fabric.md) for details on the data
 Azure Monitor doesn't collect any platform metrics or resource logs for Service Fabric. You can monitor and collect:
 
 - Service Fabric system, node, and application events. For the full event listing, see [List of Service Fabric events](service-fabric-diagnostics-event-generation-operational.md).
-- Windows performance counters on nodes and applications. For the list of performance counters, see [Performance metrics](service-fabric-diagnostics-event-generation-perf.md).
+- Windows performance counters on nodes and applications. For the list of performance counters, see [Performance metrics](#performance-metrics).
 - Cluster, node, and system service health data. You can use the [FabricClient.HealthManager property](/dotnet/api/system.fabric.fabricclient.healthmanager) to get the health client to use for health related operations, like report health or get entity health.
 - Metrics for the guest operating system (OS) that runs on a cluster node, through one or more agents that run on the guest OS.
 
@@ -27,9 +27,74 @@ Azure Monitor doesn't collect any platform metrics or resource logs for Service
   > [!NOTE]
   > The Azure Monitor agent replaces the previously-used Azure Diagnostics extension and Log Analytics agent. For more information, see [Overview of Azure Monitor agents](/azure/azure-monitor/agents/agents-overview).
 
+## Performance metrics
+
+Metrics should be collected to understand the performance of your cluster as well as the applications running in it. For Service Fabric clusters, we recommend collecting the following performance counters.
+
+### Nodes
+
+For the machines in your cluster, consider collecting the following performance counters to better understand the load on each machine and make appropriate cluster scaling decisions.
+
+| Counter Category | Counter Name |
+| --- | --- |
+| Logical Disk | Logical Disk Free Space |
+| PhysicalDisk(per Disk) | Avg. Disk Read Queue Length |
+| PhysicalDisk(per Disk) | Avg. Disk Write Queue Length |
+| PhysicalDisk(per Disk) | Avg. Disk sec/Read |
+| PhysicalDisk(per Disk) | Avg. Disk sec/Write |
+| PhysicalDisk(per Disk) | Disk Reads/sec |
+| PhysicalDisk(per Disk) | Disk Read Bytes/sec |
+| PhysicalDisk(per Disk) | Disk Writes/sec |
+| PhysicalDisk(per Disk) | Disk Write Bytes/sec |
+| Memory | Available MBytes |
+| PagingFile | % Usage |
+| Processor(Total) | % Processor Time |
+| Process (per service) | % Processor Time |
+| Process (per service) | ID Process |
+| Process (per service) | Private Bytes |
+| Process (per service) | Thread Count |
+| Process (per service) | Virtual Bytes |
+| Process (per service) | Working Set |
+| Process (per service) | Working Set - Private |
+| Network Interface(all-instances) | Bytes recd |
+| Network Interface(all-instances) | Bytes sent |
+| Network Interface(all-instances) | Bytes total |
+| Network Interface(all-instances) | Output Queue Length |
+| Network Interface(all-instances) | Packets Outbound Discarded |
+| Network Interface(all-instances) | Packets Received Discarded |
+| Network Interface(all-instances) | Packets Outbound Errors |
+| Network Interface(all-instances) | Packets Received Errors |
+
+### .NET applications and services
+
+Collect the following counters if you are deploying .NET services to your cluster. 
+
+| Counter Category | Counter Name |
+| --- | --- |
+| .NET CLR Memory (per service) | Process ID |
+| .NET CLR Memory (per service) | # Total committed Bytes |
+| .NET CLR Memory (per service) | # Total reserved Bytes |
+| .NET CLR Memory (per service) | # Bytes in all Heaps |
+| .NET CLR Memory (per service) | Large Object Heap size |
+| .NET CLR Memory (per service) | # GC Handles |
+| .NET CLR Memory (per service) | # Gen 0 Collections |
+| .NET CLR Memory (per service) | # Gen 1 Collections |
+| .NET CLR Memory (per service) | # Gen 2 Collections |
+| .NET CLR Memory (per service) | % Time in GC |
+
+### Service Fabric's custom performance counters
+
+Service Fabric generates a substantial amount of custom performance counters. If you have the SDK installed, you can see the comprehensive list on your Windows machine in your Performance Monitor application (Start > Performance Monitor).
+
+In the applications you are deploying to your cluster, if you are using Reliable Actors, add counters from `Service Fabric Actor` and `Service Fabric Actor Method` categories (see [Service Fabric Reliable Actors Diagnostics](service-fabric-reliable-actors-diagnostics.md)).
+
+If you use Reliable Services or Service Remoting, we similarly have `Service Fabric Service` and `Service Fabric Service Method` counter categories that you should collect counters from, see [monitoring with service remoting](service-fabric-reliable-serviceremoting-diagnostics.md) and [reliable services performance counters](service-fabric-reliable-services-diagnostics.md#performance-counters).
+
+If you use Reliable Collections, we recommend adding the `Avg. Transaction ms/Commit` from the `Service Fabric Transactional Replicator` to collect the average commit latency per transaction metric.
+
 [!INCLUDE [horz-monitor-ref-logs-tables](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-logs-tables.md)]
 
-### Service Fabric Clusters
+### Service Fabric clusters
 Microsoft.ServiceFabric/clusters
 
 - [AzureActivity](/azure/azure-monitor/reference/tables/AzureActivity#columns)
@@ -44,4 +109,3 @@ Microsoft.ServiceFabric/clusters
 - See [Monitor Service Fabric](monitor-service-fabric.md) for a description of monitoring Service Fabric.
 - See [Monitor Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource) for details on monitoring Azure resources.
 - See [List of Service Fabric events](service-fabric-diagnostics-event-generation-operational.md) for the list of Service Fabric system, node, and application events.
-- See [Performance metrics](service-fabric-diagnostics-event-generation-perf.md) for the list of Windows performance counters on nodes and applications.