bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

Set up monitoring for Onyx Fetch API endpoint

RESOLVED FIXED

Status

Content Services Graveyard
Tiles: Ops
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: oyiptong, Assigned: mostlygeek)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: .?)

(Reporter)

Description

3 years ago
Please set up monitoring for Onyx endpoints

Here's an example command:

$ curl -I  https://tiles.services.mozilla.com/v2/links/fetch/en-US

A correct result would be:

HTTP/1.1 303 SEE OTHER
Content-Length: 405
Content-Type: text/html; charset=utf-8
Date: Wed, 18 Mar 2015 18:13:08 GMT
Location: https://dtex4kvbppovt.cloudfront.net/desktop/CA/en-US.5c3eb03e7b87180301636431e10fcb3f02f7b210.json
Connection: keep-alive

Where 303 is the status code, and Location is a CDN location

Updated

3 years ago
Assignee: nobody → dthornton
(Assignee)

Comment 1

3 years ago
Actually it would be better if we updated the /__heartbeat__ endpoint. If there is no index or onyx is missing something, __heartbeat__ should return a 200 with an error message. If *everything* is ok, __heartbeat__ should return a 200 and "OK".
(Reporter)

Comment 2

3 years ago
or perhaps __hearbeat__ returns 503 Service Unavailable in case fetch is not successful?
(Reporter)

Comment 3

3 years ago
In that case, __heartbeat__ should return errors upon any errors occuring, including:

* host load balancer failing
* application server failing
* fetch API endpoint failing
* ... ?
wait, why return a 200 with an error message, and not an appropriate 500 code?

also: test script: https://github.com/mozilla/onyx/pull/1
(Assignee)

Comment 5

3 years ago
returning 200 w/ an error message is good to hit the page in a browser. Though I'm good with it returning a 500 w/ the appropriate error message too.
(Assignee)

Updated

3 years ago
Blocks: 1152557
(Assignee)

Comment 6

3 years ago
I looked at the code a bit and
Assignee: dthornton → bwong
(Assignee)

Comment 7

3 years ago
^ oops
(Assignee)

Comment 9

3 years ago
I think that is good enough for now with the implementation of __hearbeat__ in the onyx python app.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Iteration: --- → 40.3 - 11 May
Points: --- → 5
You need to log in before you can comment on or make changes to this bug.