Skip to content

Commit 98d898c

Browse files
committed
DOC-4307 Feedback update to add use cases for load balancers vs. monitoring
1 parent 057a2e9 commit 98d898c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

content/operate/rs/databases/durability-ha/db-availability.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ weight: 30
1414

1515
You can use the [database availability API]({{<relref "/operate/rs/references/rest-api/requests/bdbs/availability">}}) to verify whether a Redis Software database is available to perform read and write operations and can respond to queries from client applications. Load balancers and automated monitoring tools can use this API to monitor database availability.
1616

17-
## Check database availability
17+
## Check database availability for monitoring
1818

19-
To check the availability status of a database:
19+
To monitor database availability, use the following REST API request:
2020

2121
```sh
2222
GET /v1/bdbs/<database_id>/availability
@@ -28,9 +28,9 @@ Returns the status code 200 OK if the database is available.
2828

2929
If the database is unavailable, returns an error status code and a JSON object that contains [`error_code` and `description` fields]({{<relref "/operate/rs/references/rest-api/requests/bdbs/availability#get-db-error-codes">}}).
3030

31-
## Check local database endpoint availability
31+
## Check local database endpoint availability for load balancers
3232

33-
To check the availability of a local database endpoint:
33+
To check database availability when using a load balancer and the recommended `all-nodes` proxy policy, use the local database endpoints for each node:
3434

3535
```sh
3636
GET /v1/local/bdbs/<database_id>/endpoint/availability

0 commit comments

Comments
 (0)