coredns/plugin/health
James Hartig a469a17cdf Instead of hardcoding plugin lists in autopath/health, use interfaces. (#1306)
Switched health and autopath plugin to allow any plugins to be used instead
of a hardcoded list. I did not switch federation over since it wasn't
obvious that anything other than kubernetes could be used with it.

Fixes #1291
2017-12-12 20:40:30 +00:00
..
health.go Remove the word middleware (#1067) 2017-09-14 09:36:06 +01:00
health_test.go plugin/health: implement dyn health checks (#1214) 2017-11-13 09:52:40 +00:00
healther.go Instead of hardcoding plugin lists in autopath/health, use interfaces. (#1306) 2017-12-12 20:40:30 +00:00
README.md Instead of hardcoding plugin lists in autopath/health, use interfaces. (#1306) 2017-12-12 20:40:30 +00:00
setup.go Instead of hardcoding plugin lists in autopath/health, use interfaces. (#1306) 2017-12-12 20:40:30 +00:00
setup_test.go Remove the word middleware (#1067) 2017-09-14 09:36:06 +01:00

health

health enables a simple health check endpoint.

By default, it listens on port 8080.

Syntax

health [ADDRESS]

Optionally takes an address; the default is :8080. The health path is fixed to /health. The health endpoint returns a 200 response code and the word "OK" when CoreDNS is healthy. It returns a 503. health periodically (1s) polls plugin that exports health information. If any of the plugin signals that it is unhealthy, the server will go unhealthy too. Each plugin that supports health checks has a section "Health" in their README.

Plugins

Any plugin that implements the Healther interface will be used to report health.

Examples

Run another health endpoint on http://localhost:8091.

. {
    health localhost:8091
}