From mozilla/telemetry-dashboard#243: "When aggregates.telemetry.mozilla.org returns an error response (as in mozilla/telemetry-dashboard#242), it does not send the Access-Control-Allow-Origin header. This causes errors to appear to be CORS failures, when in fact they are HTTP errors. The server should emit the ACAO header so that the proper error messages appear in the developer console." This was filed as mozilla/python_mozaggregator#18 but somehow missed the train that would've had it refiled here in BMO.
what the priority on this Chris?
The sooner we get to it, the nicer it'll be for consumers of aggregates.tmo. tmo itself may need an additional change to react well to the error messages it'll suddenly be able to understand, before user value can be felt. On a scale from 1 to 5, I'd put it as 3 - sometime this quarter would be nice.
Component: Metrics: Pipeline → Telemetry Aggregation Service (TMO)
Priority: -- → P3
Product: Cloud Services → Data Platform and Tools
You need to log in before you can comment on or make changes to this bug.