Difference between revisions of "Health Checks"
From CitconWiki
Jump to navigationJump to search (Created page with "* red, yellow, green -- pass, warn, fail * respond with a cached value * avoiding royalty based calls as part of a health check What's the difference between a health check a...") |
(add link to TIM Group use of health checks) |
||
| Line 24: | Line 24: | ||
DR vs. "business continuity" | DR vs. "business continuity" | ||
| + | |||
| + | Health checks are part of the application contract used for orchestration at TIM Group: [[https://devblog.timgroup.com/2012/12/20/introducing-orc-and-its-agents/ Introducing Orc and Its Agents]] (see part 2 in the series). | ||
| + | |||
| + | Github repo for "Tucker", a library for status pages: https://github.com/tim-group/Tucker | ||
Latest revision as of 06:23, 4 October 2015
- red, yellow, green -- pass, warn, fail
- respond with a cached value
- avoiding royalty based calls as part of a health check
What's the difference between a health check and an integration test
not all health checks need to be polled you can also have services provide their own heartbeat back to a monitoring service
health check content possibility {
“service_name”: “extranet”,
“sevice_version”: “1.1.10”,
“status”: “pass”,
“dependency-status”: {
“other-api”: “connected"
“db”: “read-successful"
}
“id”: ???,
“hostname”: ???,
“instance-id”: ???
[{"subject": "value"}, {"subject": "value"}, {"subject": "value"}, {"subject": "value"}]
}
DR vs. "business continuity"
Health checks are part of the application contract used for orchestration at TIM Group: [Introducing Orc and Its Agents] (see part 2 in the series).
Github repo for "Tucker", a library for status pages: https://github.com/tim-group/Tucker
