Skip to content

Commit 2241c71

Browse files
authored
Merge pull request #197743 from craigshoemaker/aca/health-probes
[Container Apps] Health Probes: update TOC location
2 parents 28f6c23 + dc74f34 commit 2241c71

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/container-apps/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,8 +54,6 @@
5454
href: firewall-integration.md
5555
- name: Observability
5656
href: observability.md
57-
- name: Health probes
58-
href: health-probes.md
5957
- name: Authentication
6058
href: authentication.md
6159
- name: Dapr integration
@@ -80,6 +78,8 @@
8078
href: github-actions-cli.md
8179
- name: Use a custom VNET
8280
href: vnet-custom.md
81+
- name: Use health probes
82+
href: health-probes.md
8383
- name: Enable authentication
8484
items:
8585
- name: Azure Active Directory

articles/container-apps/health-probes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -155,11 +155,11 @@ containers:
155155

156156
The optional `failureThreshold` setting defines the number of attempts Container Apps tries if the probe if execution fails. Attempts that exceed the `failureThreshold` amount cause different results for each probe.
157157

158-
## Default configuration
158+
## Default configuration
159159

160160
Container Apps offers default probe settings if no probes are defined. If your app takes an extended amount of time to start, which is very common in Java, you often need to customize the probes so your container won't crash.
161161

162-
The following example demonstrates how to extend the liveness and readiness probes to accommodate an extended start-up process.
162+
The following example demonstrates how to configure the liveness and readiness probes in order to extend the startup times.
163163

164164
```json
165165
"probes": [

0 commit comments

Comments
 (0)