Skip to content

Commit

Permalink
Merge pull request docker#678 from joaofnfernandes/dtr-health-checks
Browse files Browse the repository at this point in the history
Add more information about DTR healthchecks
  • Loading branch information
joaofnfernandes authored Nov 22, 2016
2 parents 28d9764 + c8c05e6 commit 730f225
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 1 deletion.
2 changes: 1 addition & 1 deletion datacenter/dtr/2.1/guides/high-availability/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ Make sure you configure your load balancer to:

* Load-balance TCP traffic on ports 80 and 443,
* Not terminate HTTPS connections,
* Use the `/load_balancer_status` endpoint on each DTR replica, to check if
* Use the `/health` endpoint on each DTR replica, to check if
the replica is healthy and if it should remain on the load balancing pool or
not.

Expand Down
15 changes: 15 additions & 0 deletions datacenter/dtr/2.1/guides/monitor-troubleshoot/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,21 @@ resources, and logs.

![](../images/monitor-2.png)

## Health checks

DTR also exposes several endpoints you can use to assess if a DTR replica
is healthy or not:

* `/health`: Checks if the several components of a DTR replica are healthy, and
returns a simple json response. This is useful for load balancing or other
automated health check tasks.
* `/load_balancer_status`: Checks if the several components of a DTR replica
can be reached, and displays that information in a table. This is useful for
an administrator to gauge the status of a DTR replica.
* `/nginx_status`: Returns the number of connections being handled by the
NGINX front-end used by DTR.
* `/api/v0/meta/cluster_status`: Returns extensive information about all DTR
replicas.

## Where to go next

Expand Down

0 comments on commit 730f225

Please sign in to comment.