Status

defect
RESOLVED WONTFIX
6 years ago
6 years ago

People

(Reporter: cade, Assigned: capilkey)

Tracking

Details

(Reporter)

Description

6 years ago
hitting the health check endpoint should use Basic Authentication and provide DB and ES health stats.

Hitting it with `?elb=true` (not sure if thats exactly right, will confirm with jp) should be public, and simply return 200 to indicate the server is active.
(Reporter)

Updated

6 years ago
Status: NEW → ASSIGNED
(Reporter)

Comment 1

6 years ago
I'm not sure I can do one route like that, so I'll do 

`/healthcheck` with baisc auth and make
`/healthcheck/elb` public

Comment 2

6 years ago
You can do it as one route, just check req.query for an `elb` key
(Reporter)

Updated

6 years ago
Assignee: cade → capilkey
Jon, can you please weigh in on this with a strategy for him to move forward?  We were discussing in class, and I think we just need some decisions made about how to tackle things.
Flags: needinfo?(jon)
I think we should WONTFIX this bug.

We looked at the mongoose/mongodb API bits and there's no reliable way of saying "this connection is active". In terms of elasticsearch health status, the elasticsearch API already provides that at "/_cluster/health?pretty=true"
Flags: needinfo?(jon)
(Reporter)

Comment 5

6 years ago
This sounds sane to me. Ideally, I want us to level up on our ElasticSearch ninja skills and drop mongo altogether. I think we'd see some incredible performance wins in the process.
(Assignee)

Comment 6

6 years ago
Marking it as WONTFIX sounds good to me.
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.