Closed Bug 1253474 Opened 8 years ago Closed 8 years ago

Configure a new endpoint on our edge servers to accept /submit/sslreports

Categories

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

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: kparlante, Assigned: whd)

References

Details

To start accepting SSL Report data...
Triaging to P2, should happen in next sprint or two. Ideally use the new edge, so waiting on 1137424
Depends on: 1137424
Priority: -- → P2
Points: --- → 2
Assignee: nobody → mreid
Submitted this PR to avoid generating a telemetry error message for each ssl reports submission:
https://github.com/mozilla-services/data-pipeline/pull/211
Submitted another PR to add the pipeline configuration for accepting and storing these submissions:
https://github.com/mozilla-services/puppet-config/pull/2043
These 2 PRs have been merged. Over to whd to close when it's been deployed.
Assignee: mreid → whd
This has been deployed. I've verified that running

curl -d{} -XPOST "https://incoming.telemetry.mozilla.org/submit/sslreports/"

produces a result in:

s3://net-mozaws-prod-us-west-2-pipeline-data/sslreports-raw/20160526/
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.