Closed
Bug 1316278
Opened 8 years ago
Closed 8 years ago
ATMO V2: Implement dockerflow health check endpoints
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jezdez, Unassigned)
References
Details
Attachments
(1 file)
As mentioned here by :whd ATMO is missing some of the dockerflow health check endpoints The documentation is *I think* here: https://github.com/mozilla-services/dockerflow#containerized-app-requirements Quoting the docs: Respond to /__version__ with the contents of /app/version.json. Respond to /__heartbeat__ with a HTTP 200 or 5xx on error. This should check backing services like a database for connectivity. Respond to /__lbheartbeat__ with an HTTP 200. This is for load balancer checks and should not check backing services. Blake, can you clarify what /__heartbeat__ should specifically check in the case of atmo? Would a simple request against the Django ORM suffice? How about Redis, should that be checked, too?
Reporter | ||
Updated•8 years ago
|
Flags: needinfo?(bimsland)
Comment 1•8 years ago
|
||
I know I keep pointing at them, but normandy [1] looks like they have a good example that uses the Django checks framework [2]. I think checking both database and redis would be a good idea. [1] https://github.com/mozilla/normandy/tree/master/normandy/health [2] https://docs.djangoproject.com/en/1.10/topics/checks/
Flags: needinfo?(bimsland)
Updated•8 years ago
|
Points: --- → 1
Priority: -- → P1
Comment 2•8 years ago
|
||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•