Closed Bug 1137424 Opened 11 years ago Closed 10 years ago

Implement v2 HTTP Edge

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mreid, Assigned: trink, Mentored)

References

Details

(Whiteboard: [unifiedTelemetry])

Implement the full HTTP Edge Spec here: https://wiki.mozilla.org/CloudServices/DataPipeline/HTTPEdgeServerSpecification Using a SandboxInput, we'll have full control over the parts that couldn't easily be added to the existing Heka HttpListenInput, primarily the server's response codes.
Priority: -- → P2
Priority: P2 → P3
We will need this before cutting the "tee" server over to the Heka-based HTTP edge server. The tee is currently returning the HTTP response from the old server.
Whiteboard: [unifiedTelemetry]
Priority: P3 → P1
QA Contact: mtrinkala
Assignee: nobody → mtrinkala
QA Contact: mtrinkala
In the recent weeks the current edge server has caused two minor outages/data loss. The redesign is over due and should consist of a few days of work. Getting it in test now makes deployment viable early in Q1. For simplicity it will be an Nginx upstream module that produces a Heka message and pushes it to a Kafka topic (no decoding/validation, that will be moved from the edge back to the data warehouse loader)
Priority: P1 → P2
Points: --- → 3
After triage bumping the priority down 1 more
Priority: P2 → P3
Priority: P3 → P2
Re: the soon-to-be-ingested SSL reports, we need to update the spec (and the code) to make the "id" field in the URL optional.
Blocks: 1253472
Points: 3 → 5
Priority: P2 → P1
Status: NEW → ASSIGNED
Blocks: 1253474
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Depends on: 1269405
Blocks: 1269405
No longer depends on: 1269405
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.