- Notifications
You must be signed in to change notification settings - Fork0
Public documentation for boltopspro/up
License
boltops-pro-docs/up
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
NOTE: This repo contains only the documentation for the private BoltsOps Pro repo code.Original file:https://github.com/boltopspro/up/blob/master/README.mdThe docs are publish so they are available for interested customers.For access to the source code, you must be a paying BoltOps Pro subscriber.If are interested, you can contact us atcontact@boltops.com orhttps://www.boltops.com
Theup
command checks if services are up and running and reports CloudWatch custom metrics. It's a companion tool that is used by theUpCheck Blueprint.
- Metric Names: 1) HealthCheckStatus and 2) ResponseTime
- Useful to run this script within the network to check internal applications that cannot be pinged from the outside world.
- Tool reads a
up.yml
file in the current directory by default.
up check
The tool looks for a configuration file in these locations:
- up.yml - current directory
- config/up.yml - current directory
- ~/.up.yml - home directory (note the dot)
The up.yml looks like this:
----name:demo-web-1url:http://external-site.com/health/check/path-name:demo-web-2url:http://internal-site.private
Some of the tool's settings can be controlled with environmental variables:
Env Var | Description | Default Value |
---|---|---|
UP_CLOUDWATCH_DIMENSION_NAME | CloudWatch metric dimension name | App |
UP_CLOUDWATCH_DIMENSION_VALUE | CloudWatch metric dimension value | site name fromup.yml |
UP_CLOUDWATCH_ENABLED | Enables sending of the data to CloudWatch. | (unset) Defaults to enabled on AWS Lambda and disabled when not on Lambda. |
UP_CLOUDWATCH_NAMESPACE | CloudWatch metric namespace | UpCheck |
UP_MAX_THREADS | Max number of threads | 200 |
To install:
rake install