1014072 - Create a stable health-check URL

Status: RESOLVED WONTFIX

(Webtools :: Bouncer, defect)

Description

[Philippe M. Chiasson (:gozer)]

I'd like to see if it could be possible to create a stable bouncer URL to be used as a health-check. The reason for this is for a traffic director to assess the health of bouncer itself.

Just hitting / is no good, as it just redirects and doesn't talk to the database.
Checking a product download URL and check for a 302 Redirect is possible, but that would need hard-coding a specific product (i.e. Firefox-29.0-SSL) into the check.

I figured a /healthcheck URL that checks the database is reacheable would work, but after further thought, would it be possible to just create a 'fake' product, like 'healthcheck' and point it at some stable file, like https://ftp.mozilla.org/pub/mozilla.org/zz/marker.txt.

That way, no special code is needed in bouncer for this, and I get a stable URL to assess bouncer health that goes throught all the same code path as a regular bouncer request.

Comment 1

[Robert Helmer [:rhelmer]]

Sounds doable.

I tried setting this up on bouncer stage but it's not showing up yet, not sure if this is because sentry hasn't finished yet or because I messed something up - will dig more into it later today.

Comment 2

[Philippe M. Chiasson (:gozer)]

(In reply to Robert Helmer [:rhelmer] from comment #1)
> Sounds doable.

Fantastic, thanks!

> I tried setting this up on bouncer stage but it's not showing up yet, not
> sure if this is because sentry hasn't finished yet or because I messed
> something up - will dig more into it later today.

Great!

Comment 3

[Robert Helmer [:rhelmer]]

OK this seems to work on stage, what do you think?

https://download.allizom.org/?product=healthcheck&os=none

Comment 4

[Philippe M. Chiasson (:gozer)]

(In reply to Robert Helmer [:rhelmer] from comment #3)
> OK this seems to work on stage, what do you think?
> 
> https://download.allizom.org/?product=healthcheck&os=none

Verified as working ;-)

Only question I have is wether picking /zz/marker.txt is the best choice, as it's importance might not be readily obvious.

How about picking this instead:

https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/latest/KEY

Should *always* be there and is part of the release process, correct ?

Comment 5

[Philippe M. Chiasson (:gozer)]

Only recently discovered the ?print=1 argument, going thru the whole normal code path, and printing the redirect instead of redirecting, so this

https://download.mozilla.org/?product=firefox-latest&print=1

Ends up doing exactly what I wanted.