[login.wm.o] Integrate MySQL error handling with /healthcheck endpoint

RESOLVED WONTFIX

Status

defect
RESOLVED WONTFIX
6 years ago
6 years ago

People

(Reporter: sedge, Assigned: sedge)

Tracking

Details

(Assignee)

Description

6 years ago
The current implementation of mongoDB error handling is a good candiate for integration into the /healthcheck endpoint, as it would expose more useful information to administrators about the state of the login server.
(Assignee)

Updated

6 years ago
Status: NEW → ASSIGNED
Whiteboard: u=dev c=login → u=dev c=login p=1 s=2013w20
Does this need to be done for our first integration build?
No
Whiteboard: u=dev c=login p=1 s=2013w20

Comment 3

6 years ago
do we still need to do this?
Flags: needinfo?(kieran.sedgwick)
(Assignee)

Comment 4

6 years ago
I would say so. :jp would know more.
Flags: needinfo?(kieran.sedgwick) → needinfo?(johns)

Comment 5

6 years ago
My hope would be that yes, the health check verbose mode (not healthcheck?elb=true) should check this and report on it.

One mistake I've been seeing on some apps is devs telling the health check to decide whether or not to keep the app running.  Please do NOT make your app staying running on the web tier nodes dependent on health checks answering yes.
Flags: needinfo?(johns)
(Assignee)

Updated

6 years ago
Summary: [login.wm.o] Integrate mongoDB error handling with /healthcheck endpoint → [login.wm.o] Integrate MySQL error handling with /healthcheck endpoint
(Assignee)

Updated

6 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.