Merge branch 'v1.9' into patch-1

daprdocs/content/en/concepts/resiliency-concept.md

@@ -0,0 +1,39 @@
+---
+type: docs
+title: "Resiliency"
+linkTitle: "Resiliency"
+weight: 400
+description: "Configure policies and monitor app and sidecar health"
+---
+
+Distributed applications are commonly comprised of many microservices, with dozens - sometimes hundreds - of instances scaling across underlying infrastructure. As these distributed solutions grow in size and complexity, the potential for system failures inevitably increases. Service instances can fail or become unresponsive due to any number of issues, including hardware failures, unexpected throughput, or application lifecycle events, such as scaling out and application restarts. Designing and implementing a self-healing solution with the ability to detect, mitigate, and respond to failure is critical.
+
+## Resiliency Policies
+<img src="/images/resiliency_diagram.png" width="1200" alt="Diagram showing the resiliency applied to Dapr APIs">
+
+Dapr provides a capability for defining and applying fault tolerance resiliency policies to your application. You can define policies for following resiliency patterns:
+
+- Timeouts
+- Retries/back-offs
+- Circuit breakers
+
+These policies can be applied to any Dapr API calls when calling components with a [resiliency spec]({{< ref resiliency-overview >}}).
+
+## App Health Checks
+<img src="/images/observability-app-health.webp" width="800" alt="Diagram showing the app health feature. Running Dapr with app health enabled causes Dapr to periodically probe the app for its health">
+
+Applications can become unresponsive for a variety of reasons. For example, they are too busy to accept new work, could have crashed, or be in a deadlock state. Sometimes the condition can be transitory or persistent.
+
+Dapr provides a capability for monitoring app health through probes that check the health of your application and react to status changes. When an unhealthy app is detected, Dapr stops accepting new work on behalf of the application.
+
+Read more on how to apply [app health checks]({{< ref app-health >}}) to your application.
+
+## Sidecar Health Checks
+<img src="/images/sidecar-health.png" width="800" alt="Diagram showing the app health feature. Running Dapr with app health enabled causes Dapr to periodically probe the app for its health">
+
+Dapr provides a way to determine its health using an [HTTP `/healthz` endpoint]({{< ref health_api.md >}}). With this endpoint, the *daprd* process, or sidecar, can be:
+
+- Probed for its health
+- Determined for readiness and liveness
+
+Read more on about how to apply [dapr health checks]({{< ref sidecar-health >}}) to your application.

daprdocs/content/en/developing-applications/building-blocks/observability/sidecar-health.md

@@ -6,7 +6,7 @@ weight: 200
 description: Dapr sidecar health checks
 ---
 
-Dapr provides a way to [determine its health using an [HTTP `/healthz` endpoint]({{< ref health_api.md >}}). With this endpoint, the *daprd* process, or sidecar, can be:
+Dapr provides a way to determine its health using an [HTTP `/healthz` endpoint]({{< ref health_api.md >}}). With this endpoint, the *daprd* process, or sidecar, can be:
 
 - Probed for its health
 - Determined for readiness and liveness

daprdocs/content/en/developing-applications/integrations/Azure/authenticating-azure.md

@@ -84,7 +84,7 @@ To start, create a new Azure AD application, which will also be used as Service
 
 Prerequisites:
 
-- [Azure Subscription](https://azure.microsoft.com/free/)
+- Azure Subscription
 - [Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli)
 - [jq](https://stedolan.github.io/jq/download/)
 - OpenSSL (included by default on all Linux and macOS systems, as well as on WSL)

daprdocs/content/en/developing-applications/integrations/Azure/azure-kubernetes-service-extension.md

@@ -7,7 +7,7 @@ weight: 4000
 ---
 
 # Prerequisites
-- [Azure subscription](https://azure.microsoft.com/free/?WT.mc_id=A261C142F)
+- Azure subscription
 - [Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli-windows?tabs=azure-cli) and the ***aks-preview*** extension.
 - [Azure Kubernetes Service (AKS) cluster](https://docs.microsoft.com/azure/aks/tutorial-kubernetes-deploy-cluster?tabs=azure-cli)
 

daprdocs/content/en/getting-started/tutorials/configure-state-pubsub.md

@@ -64,9 +64,7 @@ For Kubernetes:
 {{% /codetab %}}
 
 {{% codetab %}}
-<!-- IGNORE_LINKS -->
-Verify you have an [Azure subscription](https://azure.microsoft.com/free/).
-<!-- END_IGNORE -->
+Verify you have an Azure subscription.
 
 1. Open and log into the [Azure portal](https://ms.portal.azure.com/#create/Microsoft.Cache) to start the Azure Redis Cache creation flow. 
 1. Fill out the necessary information.

daprdocs/content/en/operations/resiliency/resiliency-overview.md

@@ -9,8 +9,6 @@ description: "Configure Dapr retries, timeouts, and circuit breakers"
  Resiliency is currently a preview feature. Before you can utilize a resiliency spec, you must first [enable the resiliency preview feature]({{< ref support-preview-features >}}).
 {{% /alert %}}
 
-Distributed applications are commonly comprised of many microservices, with dozens, even hundreds, of instances for any given application. With so many microservices, the likelihood of a system failure increases. For example, an instance can fail or be unresponsive due to hardware, an overwhelming number of requests, application restarts/scale outs, or several other reasons. These events can cause a network call between services to fail. Designing and implementing your application with fault tolerance, the ability to detect, mitigate, and respond to failures, allows your application to recover to a functioning state and become self healing.
-
 Dapr provides a capability for defining and applying fault tolerance resiliency policies via a [resiliency spec]({{< ref "resiliency-overview.md#complete-example-policy" >}}). Resiliency specs are saved in the same location as components specs and are applied when the Dapr sidecar starts.  The sidecar determines how to apply resiliency policies to your Dapr API calls. In self-hosted mode, the resiliency spec must be named `resiliency.yaml`. In Kubernetes Dapr finds the named resiliency specs used by your application. Within the resiliency spec, you can define policies for popular resiliency patterns, such as:
 
 - [Timeouts]({{< ref "policies.md#timeouts" >}})

daprdocs/content/en/reference/components-reference/supported-bindings/eventgrid.md

@@ -44,7 +44,7 @@ spec:
   - name: accessKey
     value: "[AccessKey]"
   - name: topicEndpoint
-    value: "[TopicEndpoint]
+    value: "[TopicEndpoint]"
 ```
 
 {{% alert title="Warning" color="warning" %}}
@@ -102,7 +102,7 @@ _Make sure to also to add quotes around the `[HandshakePort]` in your Event Grid
 
 ```bash
 # Using random port 9000 as an example
-ngrok http -host-header=localhost 9000
+ngrok http --host-header=localhost 9000
 ```
 
 - Configure the ngrok's HTTPS endpoint and custom port to input binding metadata

daprdocs/content/en/reference/components-reference/supported-secret-stores/azure-keyvault.md

@@ -53,7 +53,7 @@ Additionally, you must provide the authentication fields as explained in the [Au
 
 ### Prerequisites
 
-- [Azure Subscription](https://azure.microsoft.com/free/)
+- Azure Subscription
 - [Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli)
 - [jq](https://stedolan.github.io/jq/download/)
 - The scripts below are optimized for a bash or zsh shell