Skip to content

Commit 0bceadf

Browse files
SaisangSaisang
authored
Merge pull request #274789 from MicrosoftDocs/main
5/9 11:00 AM IST Publish
2 parents 557a287 + 0900143 commit 0bceadf

35 files changed

+422
-108
lines changed

‎articles/ai-services/language-service/conversational-language-understanding/concepts/best-practices.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -251,3 +251,4 @@ Once the request is sent, you can track the progress of the training job in Lang
251251
Caveats:
252252
- The None Score threshold for the app (confidence threshold below which the topIntent is marked as None) when using this recipe should be set to 0. This is because this new recipe attributes a certain portion of the in domain probabiliities to out of domain so that the model is not incorrectly overconfident about in domain utterances. As a result, users may see slightly reduced confidence scores for in domain utterances as compared to the prod recipe.
253253
- This recipe is not recommended for apps with just two (2) intents, such as IntentA and None, for example.
254+
- This recipe is not recommended for apps with low number of utterances per intent. A minimum of 25 utterances per intent is highly recommended.

‎articles/aks/auto-upgrade-node-os-image.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ az provider register --namespace Microsoft.ContainerService
140140
- The `SecurityPatch` channel isn't supported on Windows OS node pools.
141141

142142
> [!NOTE]
143-
> By default, any new cluster created with an API version of `06-01-2022` or later will set the node OS auto-upgrade channel value to `NodeImage`. Any existing clusters created with an API version earlier than `06-01-2022` will have the node OS auto-upgrade channel value set to `None` by default.
143+
> By default, any new cluster created with an API version of `06-01-2023` or later (including 06-02-preview) will set the node OS auto-upgrade channel value to `NodeImage`. Any existing clusters created with an API version earlier than `06-01-2023` will have the node OS auto-upgrade channel value set to `None` by default.
144144
145145

146146
## Node OS planned maintenance windows

‎articles/api-management/api-management-gateways-overview.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,6 @@ The following tables compare features available in the following API Management
110110
| [Pass-through WebSocket](websocket-api.md) | ✔️ | ✔️ | ❌ | ✔️ |
111111
| [Pass-through gRPC](grpc-api.md) (preview) | ❌ | ❌ | ❌ | ✔️ |
112112
| [OData](import-api-from-odata.md) (preview) | ✔️ | ✔️ | ✔️ | ✔️ |
113-
| [Pass-through GraphQL](graphql-apis-overview.md) | ✔️ | ✔️ |✔️ | ✔️ |
114113
| [Azure OpenAI](azure-openai-api-from-specification.md) | ✔️ | ✔️ | ✔️ | ✔️ |
115114
| [Circuit breaker in backend](backends.md#circuit-breaker-preview) (preview) | ✔️ | ✔️ | ❌ | ✔️ |
116115
| [Load-balanced backend pool](backends.md#load-balanced-pool-preview) (preview) | ✔️ | ✔️ | ✔️ | ✔️ |

‎articles/azure-arc/kubernetes/conceptual-workload-management.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -319,4 +319,6 @@ A key point is that application configuration snapshots are versioned independen
319319
## Next steps
320320

321321
* Walk through a sample implementation to explore [workload management in a multi-cluster environment with GitOps](workload-management.md).
322-
* Explore a [multi-cluster workload management sample repository](https://github.com/microsoft/kalypso).
322+
* Explore a [multi-cluster workload management sample repository](https://github.com/microsoft/kalypso).
323+
* [Concept: CD process with GitOps](https://github.com/microsoft/kalypso/blob/main/docs/cd-concept.md).
324+
* [Sample implementation: Explore CI/CD flow with GitOps](https://github.com/microsoft/kalypso/blob/main/cicd/tutorial/cicd-tutorial.md).

‎articles/azure-arc/kubernetes/tutorial-gitops-flux2-ci-cd.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -627,4 +627,5 @@ In this tutorial, you have set up a full CI/CD workflow that implements DevOps f
627627
Advance to our conceptual article to learn more about GitOps and configurations with Azure Arc-enabled Kubernetes.
628628

629629
> [!div class="nextstepaction"]
630-
> [Conceptual CI/CD Workflow using GitOps](./conceptual-gitops-flux2-ci-cd.md)
630+
> [Concept: CD process with GitOps](https://github.com/microsoft/kalypso/blob/main/docs/cd-concept.md)
631+
> [Sample implementation: Explore CI/CD flow with GitOps](https://github.com/microsoft/kalypso/blob/main/cicd/tutorial/cicd-tutorial.md)

‎articles/azure-monitor/app/java-standalone-config.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -471,8 +471,6 @@ You can use these valid `level` values to specify in the `applicationinsights.js
471471
| TRACE (or FINEST) | TRACE | TRACE | TRACE | FINEST |
472472
| ALL | ALL | ALL | ALL | ALL |
473473

474-
You can turn off autocollected logging completedly by setting the environment variable `APPLICATIONINSIGHTS_INSTRUMENTATION_LOGGING_ENABLED` to `false`. It's on by default.
475-
476474
> [!NOTE]
477475
> If an exception object is passed to the logger, the log message (and exception object details) will show up in the Azure portal under the `exceptions` table instead of the `traces` table. If you want to see the log messages across both the `traces` and `exceptions` tables, you can write a Logs (Kusto) query to union across them. For example:
478476
>
@@ -693,6 +691,9 @@ Starting from version 3.0.3, specific autocollected telemetry can be suppressed
693691
"kafka": {
694692
"enabled": false
695693
},
694+
"logging": {
695+
"enabled": false
696+
},
696697
"micrometer": {
697698
"enabled": false
698699
},
@@ -722,6 +723,7 @@ You can also suppress these instrumentations by setting these environment variab
722723
* `APPLICATIONINSIGHTS_INSTRUMENTATION_JDBC_ENABLED`
723724
* `APPLICATIONINSIGHTS_INSTRUMENTATION_JMS_ENABLED`
724725
* `APPLICATIONINSIGHTS_INSTRUMENTATION_KAFKA_ENABLED`
726+
* `APPLICATIONINSIGHTS_INSTRUMENTATION_LOGGING_ENABLED`
725727
* `APPLICATIONINSIGHTS_INSTRUMENTATION_MICROMETER_ENABLED`
726728
* `APPLICATIONINSIGHTS_INSTRUMENTATION_MONGO_ENABLED`
727729
* `APPLICATIONINSIGHTS_INSTRUMENTATION_RABBITMQ_ENABLED`

‎articles/chaos-studio/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,8 @@
9494
items:
9595
- name: Fault library
9696
href: chaos-studio-fault-library.md
97+
- name: Experiment examples
98+
href: experiment-examples.md
9799
- name: Fault providers
98100
href: chaos-studio-fault-providers.md
99101
- name: Version compatibility

‎articles/chaos-studio/chaos-studio-fault-library.md

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ Agent-based faults are injected into **Azure Virtual Machines** or **Virtual Mac
2323
|---------------------|-----------------------------------------------------------------------------|-------------------------------------------------------------|
2424
| Windows, Linux | [CPU Pressure](#cpu-pressure) | Compute capacity loss, resource pressure |
2525
| Windows, Linux | [Kill Process](#kill-process) | Dependency disruption |
26+
| Windows | [Pause Process](#pause-process) | Dependency disruption, service disruption |
2627
| Windows, Linux | [Network Disconnect](#network-disconnect) | Network disruption |
2728
| Windows, Linux | [Network Latency](#network-latency) | Network performance degradation |
2829
| Windows, Linux | [Network Packet Loss](#network-packet-loss) | Network reliability issues |
@@ -765,6 +766,50 @@ These sample values produced ~100% disk pressure when tested on a `Standard_D2s_
765766
}
766767
```
767768

769+
### Pause Process
770+
771+
| Property | Value |
772+
|-|-|
773+
| Capability name | PauseProcess-1.0 |
774+
| Target type | Microsoft-Agent |
775+
| Supported OS types | Windows. |
776+
| Description | Pauses (suspends) the specified processes for the specified duration. If there are multiple processes with the same name, this fault suspends all of those processes. Within the fault's duration, the processes are paused repetitively at the specified interval. At the end of the duration or if the experiment is canceled, the processes will resume. |
777+
| Prerequisites | None. |
778+
| Urn | urn:csci:microsoft:agent:pauseProcess/1.0 |
779+
| Parameters (key, value) | |
780+
| processNames | Delimited JSON array of process names defining which processes are to be paused. Maximum of 4. The process name can optionally include the ".exe" extension. |
781+
| pauseIntervalInMilliseconds | Amount of time the fault waits between successive pausing attempts, in milliseconds. |
782+
| virtualMachineScaleSetInstances | An array of instance IDs when you apply this fault to a virtual machine scale set. Required for virtual machine scale sets in uniform orchestration mode. [Learn more about instance IDs](../virtual-machine-scale-sets/virtual-machine-scale-sets-instance-ids.md#scale-set-instance-id-for-uniform-orchestration-mode). |
783+
784+
#### Sample JSON
785+
786+
```json
787+
{
788+
"name": "branchOne",
789+
"actions": [
790+
{
791+
"type": "continuous",
792+
"name": "urn:csci:microsoft:agent:pauseProcess/1.0",
793+
"parameters": [
794+
{
795+
"key": "processNames",
796+
"value": "[ \"test-0\", \"test-1.exe\" ]"
797+
},
798+
{
799+
"key": "pauseIntervalInMilliseconds",
800+
"value": "1000"
801+
}
802+
],
803+
"duration": "PT10M",
804+
"selectorid": "myResources"
805+
}
806+
]
807+
}
808+
```
809+
810+
#### Limitations
811+
812+
Currently, a maximum of 4 process names can be listed in the processNames parameter.
768813

769814
### Time Change
770815

@@ -1608,6 +1653,7 @@ These sample values produced ~100% disk pressure when tested on a `Standard_D2s_
16081653
* Rules are applied at the start of the action. Any external changes to the rule during the duration of the action cause the experiment to fail.
16091654
* Creating or modifying Application Security Group rules isn't supported.
16101655
* Priority values must be unique on each NSG targeted. Attempting to create a new rule that has the same priority value as another causes the experiment to fail.
1656+
* The NSG Security Rule **version 1.1** fault supports an additional `flushConnection` parameter. This functionality has an **active known issue**: if `flushConnection` is enabled, the fault may result in a "FlushingNetworkSecurityGroupConnectionIsNotEnabled" error. To avoid this error temporarily, disable the `flushConnection` parameter or use the NSG Security Rule version **1.0** fault.
16111657

16121658

16131659
### Service Bus: Change Queue State

‎articles/chaos-studio/chaos-studio-limitations.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,9 @@ The following are known limitations in Chaos Studio.
3636
## Known issues
3737
- When selecting target resources for an agent-based fault in the experiment designer, it's possible to select virtual machines or virtual machine scale sets with an operating system not supported by the fault selected.
3838
- When running in a Linux environment, the agent-based network latency fault (NetworkLatency-1.1) can only affect **outbound** traffic, not inbound traffic. The fault can affect **both inbound and outbound** traffic on Windows environments (via the `inboundDestinationFilters` and `destinationFilters` parameters).
39-
- When filtering by Azure subscriptions from the Targets and/or Experiments page, you may experience long load times if you have many subscriptions with large numbers of Azure resources. As a workaround, filter down to the single specific subscription in question to quickly find your desired Targets and/or Experiments.
39+
- When filtering by Azure subscriptions from the Targets and/or Experiments page, you may experience long load times if you have many subscriptions with large numbers of Azure resources. As a workaround, filter down to the single specific subscription in question to quickly find your desired Targets and/or Experiments.
40+
- The NSG Security Rule **version 1.1** fault supports an additional `flushConnection` parameter. This functionality has an **active known issue**: if `flushConnection` is enabled, the fault may result in a "FlushingNetworkSecurityGroupConnectionIsNotEnabled" error. To avoid this error temporarily, disable the `flushConnection` parameter or use the NSG Security Rule version **1.0** fault.
41+
4042

4143
## Next steps
4244
Get started creating and running chaos experiments to improve application resilience with Chaos Studio by using the following links:

‎articles/chaos-studio/experiment-examples.md

Lines changed: 226 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,226 @@
1+
---
2+
title: Azure CLI & Azure portal example experiments
3+
description: See real examples of creating various chaos experiments in the Azure portal and CLI.
4+
services: chaos-studio
5+
author: nikhilkaul-msft
6+
ms.topic: reference
7+
ms.date: 05/07/2024
8+
ms.author: abbyweisberg
9+
ms.reviewer: nikhilkaul
10+
ms.service: chaos-studio
11+
ms.custom: none
12+
---
13+
14+
# Example Experiments
15+
16+
This article provides examples for creating experiments from your command line (CLI) and Azure portal parameter examples for various experiments. You can copy and paste the following commands into the CLI or Azure portal, and edit them for your specific resources.
17+
18+
Here's an example of where you would copy and paste the Azure portal parameter into:
19+
20+
[![Screenshot that shows Azure portal parameter location.](images/azure-portal-parameter-examples.png)](images/azure-portal-parameter-examples.png#lightbox)
21+
22+
> [!NOTE]
23+
> Make sure your experiment has permission to operate on **ALL** resources within the experiment. These examples exclusively use **System-assigned managed identity**, but we also support User-assigned managed identity. For more information, see [Experiment permissions](chaos-studio-permissions-security.md).
24+
><br>
25+
><br>
26+
>View all available role assignments [here](chaos-studio-fault-providers.md) to determine which permissions are required for your target resources.
27+
28+
---
29+
Azure Kubernetes Service (AKS) Network Delay
30+
---
31+
32+
### [Azure CLI](#tab/azure-CLI)
33+
```AzCLI
34+
PUT https://management.azure.com/subscriptions/6b052e15-03d3-4f17-b2e1-be7f07588291/resourceGroups/exampleRG/providers/Microsoft.Chaos/experiments/exampleExperiment?api-version=2024-01-01
35+
36+
{
37+
38+
"identity": {
39+
"type": "SystemAssigned",
40+
"principalId": "35g5795t-8sd4-5b99-a7c8-d5asdh9as7",
41+
"tenantId": "asd79ash-7daa-95hs-0as8-f3md812e3md"
42+
},
43+
"tags": {},
44+
"location": "westus",
45+
"properties": {
46+
"provisioningState": "Succeeded",
47+
"selectors": [
48+
{
49+
"type": "List",
50+
"targets": [
51+
{
52+
"id": "/subscriptions/123hdq8-123d-89d7-5670-123123/resourceGroups/aks_network_delay_experiment/providers/Microsoft.ContainerService/managedClusters/nikhilAKScluster/providers/Microsoft.Chaos/targets/Microsoft-AzureKubernetesServiceChaosMesh",
53+
"type": "ChaosTarget"
54+
}
55+
],
56+
"id": "Selector1"
57+
}
58+
],
59+
"steps": [
60+
{
61+
"name": "AKS network latency",
62+
"branches": [
63+
{
64+
"name": "AKS network latency",
65+
"actions": [
66+
{
67+
"type": "continuous",
68+
"selectorId": "Selector1",
69+
"duration": "PT5M",
70+
"parameters": [
71+
{
72+
"key": "jsonSpec",
73+
"value": "{\"action\":\"delay\",\"mode\":\"all\",\"selector\":{\"namespaces\":[\"default\"]},\"delay\":{\"latency\":\"200ms\",\"correlation\":\"100\",\"jitter\":\"0ms\"}}"
74+
}
75+
],
76+
"name": "urn:csci:microsoft:azureKubernetesServiceChaosMesh:networkChaos/2.1"
77+
}
78+
]
79+
}
80+
]
81+
}
82+
]
83+
}
84+
}
85+
86+
```
87+
88+
89+
### [Azure portal parameters](#tab/azure-portal)
90+
91+
```Azure portal
92+
{"action":"delay","mode":"all","selector":{"namespaces":["default"]},"delay":{"latency":"200ms","correlation":"100","jitter":"0ms"}}
93+
```
94+
---
95+
Azure Kubernetes Service (AKS) Pod Failure
96+
---
97+
98+
### [Azure CLI](#tab/azure-CLI)
99+
```AzCLI
100+
PUT https://management.azure.com/subscriptions/6b052e15-03d3-4f17-b2e1-be7f07588291/resourceGroups/exampleRG/providers/Microsoft.Chaos/experiments/exampleExperiment?api-version=2024-01-01
101+
102+
{
103+
104+
"identity": {
105+
"type": "SystemAssigned",
106+
"principalId": "35g5795t-8sd4-5b99-a7c8-d5asdh9as7",
107+
"tenantId": "asd79ash-7daa-95hs-0as8-f3md812e3md"
108+
},
109+
"tags": {},
110+
"location": "westus",
111+
"properties": {
112+
"provisioningState": "Succeeded",
113+
"selectors": [
114+
{
115+
"type": "List",
116+
"targets": [
117+
{
118+
"id": "/subscriptions/123hdq8-123d-89d7-5670-123123/resourceGroups/aks_pod_fail_experiment/providers/Microsoft.ContainerService/managedClusters/nikhilAKScluster/providers/Microsoft.Chaos/targets/Microsoft-AzureKubernetesServiceChaosMesh",
119+
"type": "ChaosTarget"
120+
}
121+
],
122+
"id": "Selector1"
123+
}
124+
],
125+
"steps": [
126+
{
127+
"name": "AKS pod kill",
128+
"branches": [
129+
{
130+
"name": "AKS pod kill",
131+
"actions": [
132+
{
133+
"type": "continuous",
134+
"selectorId": "Selector1",
135+
"duration": "PT5M",
136+
"parameters": [
137+
{
138+
"key": "jsonSpec",
139+
"value": "{\"action\":\"pod-failure\",\"mode\":\"all\",\"duration\":\"600s\",\"selector\":{\"namespaces\":[\"autoinstrumentationdemo\"]}}}"
140+
}
141+
],
142+
"name": "urn:csci:microsoft:azureKubernetesServiceChaosMesh:podChaos/2.1"
143+
}
144+
]
145+
}
146+
]
147+
}
148+
]
149+
}
150+
}
151+
152+
```
153+
154+
155+
### [Azure portal parameters](#tab/azure-portal)
156+
157+
```Azure portal
158+
{"action":"pod-failure","mode":"all","duration":"600s","selector":{"namespaces":["autoinstrumentationdemo"]}}
159+
```
160+
---
161+
Azure Kubernetes Service (AKS) Memory Stress
162+
---
163+
164+
### [Azure CLI](#tab/azure-CLI)
165+
```AzCLI
166+
PUT https://management.azure.com/subscriptions/6b052e15-03d3-4f17-b2e1-be7f07588291/resourceGroups/exampleRG/providers/Microsoft.Chaos/experiments/exampleExperiment?api-version=2024-01-01
167+
168+
{
169+
170+
"identity": {
171+
"type": "SystemAssigned",
172+
"principalId": "35g5795t-8sd4-5b99-a7c8-d5asdh9as7",
173+
"tenantId": "asd79ash-7daa-95hs-0as8-f3md812e3md"
174+
},
175+
"tags": {},
176+
"location": "westus",
177+
"properties": {
178+
"provisioningState": "Succeeded",
179+
"selectors": [
180+
{
181+
"type": "List",
182+
"targets": [
183+
{
184+
"id": "/subscriptions/123hdq8-123d-89d7-5670-123123/resourceGroups/aks_memory_stress_experiment/providers/Microsoft.ContainerService/managedClusters/nikhilAKScluster/providers/Microsoft.Chaos/targets/Microsoft-AzureKubernetesServiceChaosMesh",
185+
"type": "ChaosTarget"
186+
}
187+
],
188+
"id": "Selector1"
189+
}
190+
],
191+
"steps": [
192+
{
193+
"name": "AKS memory stress",
194+
"branches": [
195+
{
196+
"name": "AKS memory stress",
197+
"actions": [
198+
{
199+
"type": "continuous",
200+
"selectorId": "Selector1",
201+
"duration": "PT10M",
202+
"parameters": [
203+
{
204+
"key": "jsonSpec",
205+
"value": "{\"mode\":\"all\",\"selector\":{\"namespaces\":[\"autoinstrumentationdemo\"]},\"stressors\":{\"memory\":{\"workers\":4,\"size\":\"95%\"}}"
206+
}
207+
],
208+
"name": "urn:csci:microsoft:azureKubernetesServiceChaosMesh:stressChaos/2.1"
209+
}
210+
]
211+
}
212+
]
213+
}
214+
]
215+
}
216+
}
217+
218+
```
219+
220+
221+
### [Azure portal parameters](#tab/azure-portal)
222+
223+
```Azure portal
224+
{"mode":"all","selector":{"namespaces":["autoinstrumentationdemo"]},"stressors":{"memory":{"workers":4,"size":"95%"}}
225+
```
226+
---

0 commit comments

Comments
 (0)