Skip to content

daemonza/fleetHealth

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Fleet health

For Fleet Health to work your fleet server, needs to have it's API enabled.

To do so on CoreOS look at :

https://coreos.com/fleet/docs/latest/deployment-and-configuration.html

The easiest way to get quickly up and running is to use the docker image

docker pull daemonza/fleethealth:latest
docker run -e FH_FLEET_API=<ip>:<port> -e FH_CHECK_INTERVAL=30 daemonza/fleethealth:latest

Environment settings :

The ip/hostname and port of your fleet service. Default to 127.0.0.1 if empty

FH_FLEET_API=<ip>:<port>

Time is seconds to do a fleet unit status check. Defaults to 60 seconds if empty

FH_CHECK_INTERVAL=30

You can either run fleethealth as a standalone application or use docker(recommended)

To build docker container

docker build -t fleethealth .

To run

docker run -t fleethealth

About

Go application to monitor the state of deployed services on a Fleet cluster

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages